The Welkin Suite Forum

Failing when trying to refresh project



Failing when trying to refresh project

  • Please log in to reply

#1

ramu.veligeti

    Posted 13 Jun 2016

     Hi,


    When I try to refresh my salesforce project using 'Pull from Salesforce', It is failing with 'Object reference not set to an instance of an object' error. I'm unable to continue working on TWS. Please help.


    Regards,

    Ramu



    9 replies to this topic

    #2

    kate.dulko

      Posted 14 Jun 2016

      Hi Ramu,


      Thank you for your contacting us with this information.


      I kindly ask to send us you Activity Log file after the issue is reproduced for you.

      You can find this file in the next folder: %AppData%Microsoft\AppEnv\12.0 .


      Since this is impossible for us to reproduce this issue, this file will help us to understand the reason for it.


      Thank you,

      Kate


      Kate Dulko
      Customer Relations

      The Welkin Suite

      twitter: @KateDulko
      skype id: d_katerina
      e-mail: kate.dulko@welkinsuite.com

       

        


      #3

      justin.hawkins

        Posted 15 Jul 2016

        I also experienced this issue.  I have three projects in my solution.  One was configured to use OAuth and the other two were using username and password with security token.  Only one of the projects using username/password/security token was experiencing the issue.  I cleared the username, password, and security token from the project properties for the project experiencing the problem.  I then saved and closed the solution.  When I reopened the solution, I was prompted to re-authorize using OAuth the project that was experiencing the issue.  After doing the re-authorization for the project, I was able to successfully pull from Salesforce without getting the error.



        #4

        kate.dulko

          Posted 15 Jul 2016

          Hi Justin,


          Thank you for all the details that you provided us.

          We got your bug report with the attached log file.


          Since this is impossible for us to reproduce this issue, we are looking for any additional information. Your comments can help us a lot.

          In addition, may I please clarify with you what types of the metadata are included to your pull process?


          We appreciate your help.


          Regards,

          Kate


          Kate Dulko
          Customer Relations

          The Welkin Suite

          twitter: @KateDulko
          skype id: d_katerina
          e-mail: kate.dulko@welkinsuite.com

           

            


          #5

          justin.hawkins

            Posted 15 Jul 2016

            The metadata for the failed project included:

            • classes
            • components
            • objects
            • pages
            • triggers


            #6

            kate.dulko

              Posted 15 Jul 2016

              Hi again Justin,


              Thank you for your reply.

              I'll add this information to our investigation process.


              As a side note, I'll keep you updated when the issue will be solved in The Welkin Suite.


              Best Regards,

              Kate


              Kate Dulko
              Customer Relations

              The Welkin Suite

              twitter: @KateDulko
              skype id: d_katerina
              e-mail: kate.dulko@welkinsuite.com

               

                


              #7

              laszlo.foldi

                Posted 02 Aug 2016

                I've also experienced this issue, but only when using OAuth. Otherwise (with token) it works okay.



                #8

                kate.dulko

                  Posted 02 Aug 2016

                  Hi,


                  Thank you for your post.


                  We are going to release the updated 0.30.7 version of The Welkin Suite tonight.

                  This version includes the fix for the current issue.


                  I kindly ask you to update the IDE and let us known if the issue is reproduced after this.


                  Thak you,

                  Kate 


                  Kate Dulko
                  Customer Relations

                  The Welkin Suite

                  twitter: @KateDulko
                  skype id: d_katerina
                  e-mail: kate.dulko@welkinsuite.com

                   

                    


                  #9

                  justin.hawkins

                    Posted 04 Aug 2016

                    I'm still experiencing the issue after updating.  I think I have narrowed down the steps to reproduce this on my end.  When opening my project, if my OAuth token has expired, I'm prompted to Re-Authorize.  I click Cancel instead of Authorize.  Later, when I go to pull from Salesforce for my project, I get the error message from the original post.  In this case, I would expect to be re-prompted to Authorize because I still have an expired token.


                    In some cases, I don't want to Authorize using OAuth at the time my project loads because I'm working in a different sandbox within the Salesforce UI.  Authorizing to a different sandbox within TWS will cause me to be logged out of the current sandbox (Salesforce limitation of only being able to log into a single sandbox at a time).  Being able to use OAuth to re-authorize would be helpful outside of just on the project load.



                    #10

                    kate.dulko

                      Posted 04 Aug 2016

                      Hi Justin,


                      Thank you for your investigation.


                      The issue related to the failed pull due to the expired OAuth credentials is known for us. The IDE doesn't handle this correctly. Our developers are working on solving this case. 

                      Anyway, after your token becomes expired you should connect to your Organization to refresh your files from Salesforce.


                      Currently, as a workaround you can change your credentials from OAuth to the saved ones inside your project. Please open the context menu of your project in the Solution Explorer, click the 'Properties' item. In the appeared window you can enter your credentials and save them.

                      In this case, you can continue your working process with your TWS project without logout from another your Organization on Salesforce.


                      Please let us know if this workaround is acceptable for you.


                      Thank you,

                      Kate


                      Kate Dulko
                      Customer Relations

                      The Welkin Suite

                      twitter: @KateDulko
                      skype id: d_katerina
                      e-mail: kate.dulko@welkinsuite.com

                       

                        





                      Boost Your Productivity. Get Started Today

                      Try Free Trial