I am on the version 1.0.23.4 and today I am getting object not set to an instance of an object when I try to pull from salesforce. The error is present no matter if I do that on the project root or on the classes folder. It displays the popup where I can check the folders but after clicking the next button it displays the above error message. Any idea what can be wrong?
Object not set to an instance of an object on Pull from salesforce
#1
Posted 14 Oct 2016
#2
Posted 17 Oct 2016
Thank you for you post.
The issue you are faced with is known to us. This will be solved in the next version of TWS that will be available for you this week.
This is related to the Aura Definition Bundle metadata.
Currently, you can create a new project without Lightning metadata files to continue your working process till the fix of the issue will be released.
Regards,
Kate
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com
#3
Posted 17 Oct 2016
Thank you for the answer. However, I don't have any lightning metadata in my project and I was able to create a new Project. The Problem is while trying to Pull From Salesforce. Currently I can not proceed working with this Project in TWS and need to go to Force.com IDE, again :(
#4
Posted 17 Oct 2016
Thank you for your response.
I kindly ask you to reproduce the issue related to the failed pull again and right after this please send us a bug report directly from TWS. You ca find this option in the Main Menu -> Help -> Report a Bug. Please mark the checkbox 'Attach Log file'. This way we will receive your Activity Log file that can help us to understand the reason for your issue.
Thank you,
Kate
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com
#5
Posted 17 Oct 2016
#6
Posted 17 Oct 2016
The reason for the failed pull in your case is related to the queries for the Aura Definition Bundle metadata from TWS to your Salesforce Org.
We are going to release the updated version of the IDE that includes the fix for this issue the nearest days.
Thank you for your collaboration.
Regards,
Kate
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com
#7
Posted 18 Oct 2016
#8
Posted 18 Oct 2016
Thank you for your post.
Tonight we are going to release the Spire R2 version of The Welkin Suite IDE. This version will include the fix for the failed pull that you have described.
This issue isn't related to using the OAuth authentication. The request to refresh your OAuth token is the another issue. The fix for this will be released in the Spire R2 version of the IDE also.
I kindly ask you to let us know if these issues are reproduced for your after TWS updating to the new version.
Regards,
Kate
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com
#9
Posted 19 Oct 2016
Thank you for your effort!
#10
Posted 19 Oct 2016
Thank you for your feedback.
Please contact us if you are faced with any other issues.
Regards,
Kate
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com