Hi Tim,

Thank you for your bug report.

This issue can be reproduced when you open another project after the work with the previous one. 

The reason for this issue is that the IDE doesn't change the .sfproj file for saving. The changes are not saved to the previous .sfproj file because this is not actual for that file, but these changes are not saved to the necessary file. At the same time, all the changes are saved in the separate file you are working with.

Our developers will solve this issue as soon as possible.

As a workaround, you can restart TWS before opening another project.

Regards,

Kate

Thanks for the reply, Kate.  Is this on a per-session basis?  I do have multiple projects, but the old ones are just archives and I never touch them any more.  If I only open a single project file after completely closing Welkin Suite and rebooting my computer, but I still experience the issue, is this a different bug from the one you described?  Or does the "stuck" project file persist across sessions of closing/reopening Welkin Suite?

Thanks again!

Hi Tim,

Thank you for your response.

In this case, this is the new issue for us. 

The bug, that I have described, is reproduced during the single TWS session.

Our developers will investigate your issue more detailed.

Since this is impossible for us to reproduce this issue, may I please contact you for some additional information if this is necessary?

Thank you,

Kate

I am currently receiving the same issue.  

I cannot build my project because I get "File has pending server changes. Please pull first" constantly. Restarting TWS doesn't resolve this issue, either.  I really don't want to have to create a new project and start over, as I'll lose all of my local history.

I've discovered that this happens often when there are multiple developers working in the same Salesforce sandbox.  Whenever a co-worker checks his files in, I was receiving this error message.  That really shouldn't stop me from push my changes to Salesforce, though!  (Why should I care if my co-worker updated files?  I need to push my files to SF! )  

But now it's just stuck and I get the message every time I try to build.  

Switching back and using the SF developer console...

Quick update:

I told my co-workers to stop checking things in. They sat on their hands while I restarted TWS and rebuild the project, TWS wanted me to resolve a merge issue with my file. I was then able to build the project successfully.  So perhaps it's just an issue that whenever I want to push files to SF, I have to have the latest versions of all the project files.  But this seems to cripple the ability to work in a sandbox with multiple developers who are uploading files all the time, if I have to pull from SF every time I want to push a file to SF! 

Hi John,

Thank you for your comments.

The step related to comparing your local files which you want to Build with these files on Salesforce is necessary to avoid removing new changes which were made by somebody else while you were working with the previous version of them. The IDE compares the files hash for this. If this is different, then the pull is required.

Currently, we are discussing another workflow in the 'Force Local Changes To Overwrite Salesforce' topic. You can share your additional suggestions there. 

The issue related to the required pull when there are no differences between your local files and these files on SF is present in our agenda. 

We will work on this as soon as possible.

Best Regards,

Kate

Hello, Kata,

Has a FIX  for this issue been developed. its happening to me and I have tried to Pull form SF and all of that jazz. still will not let me build. 

what more can I do?

Hi Eric,

Thank you for your post.

Our developers are working on solving this issue. We have found several reasons for this case.

The nearest version of the Welkin Suite will include these fixes.

May I please clarify with if you are working with one TWS project or change several projects in the IDE?

Thank you,

Kate

Kate, I, on 0.30.7.4 I only have one project open at a time. only using TWS on one project so its the only thing I have going. I can not build the project at all now. Not sure what I need to do to fix this.

Hi again Eric,

Thank you for your response.

As a workaround, please download a new project from this Organization.

I kindly ask you to let us know if the issue is reproduced on the re-created project. In addition, in this case please send us a bug report from the IDE with the attached lActility Log file. You can find this option in the Main Menu -> Help -> Report a bug. Please enter your email for your reply.

Thank you,

Kate

I am also seeing this issue. I tried creating a new project but that had no impact. Do you have any updates? This is extremely annoying having to pull from Salesforce before each build.

Any update on this issue? It is extremely annoying. I bought the paid version figuring this was fixed with future updates but that was not the case. Tried downloading a project without any affect as well.

Hi Ben,

 

Thank you for contacting us with this question.

The previous issue that caused the error you are faced with was solved in the Beta 0.30.17 version of The Welkin Suite IDE.

 

Currently, I kindly ask you to send us a bug report directly from The Welkin Suite IDE. This option is available for you in the Main Menu -> Help -> Report a Bug.

This way we will get your log files which can help us to find a reason for your issue.

 

We will appreciate your help greatly.

Thank you,

Kate

Can you send me a link where I can download the beta version? Just sent you the bug report.

Hi again Ben,

Thank you for the bug report with the attached log files. Our developers are looking for the reason for the issue you are faced with and I will let you know about results of their investigation soon.

There was implemented a lot of new functionality and solved many bugs in Spire versions of the IDE, and Salesforce has updates that are not available for TWS Beta.

This is why the Beta version is not available for downloading. All users who downloaded it before the release of The Welkin Suite Spire can continue to use it, however, we don't distribute it anymore.  

Regards,

Kate

Dunno if it's related but I get this issue when working on VF components. When I update them, it seems TWS (or maybe SFDC itself?) wants to also recompile any VF page that includes the component. After that, if I try to make a change to the VF page, I get the pull-first message. 

Hi Dave,

Thank you for your post.

VF pages are included to the build process and are recompiled after you have changed the VF component as dependent files. The IDE updates the changed information for all the files.

After this, the 'Last Modification Date' for VF pages is changed on Salesforce while it stays the same as previously in the sfproj file related to your TWS project. This is why the pull is required for these files - to get the latest information from your Organization. Please pull your VF pages and continue your working process on them.

Please let us know if pull is required in another case.

Thank you,

Kate

There has to be a way around that VisualForce component issue.    I like the Welkin Suite as i come from .NET and was thinking of purchasing it on my own to use for work.  But this VisualForce component issue, where I need to re-download the pages that use the components is a KILLER.   My org is 8000 users, 1200 objects 50+ Million records, downloading a single file from Salesforce takes 5 minutes every time.

There has to be a better way.

Greetings,

Thank you for your post.

May I please clarify with you what version of The Welkin Suite do you have? You can check this in the Help -> About The Welkin Suite.

Our developers have worked on this issue and we solved this in Spire R13.

If you have Spire R13 or Spire R14 version of the IDE, and the issue is reproduced for you, I kindly ask you to send us a bug report directly from TWS. This option is available for you in the menu Help - > Report a Bug. Please enable the checkbox 'Attach Log File' and specify your email. This way we will receive your TWS logs and this will help us to find the reason for the issue which you are faced with.

If you have an earlier version of the IDE, please update The Welkin Suite for you locally. 

Thank you,

Kate

I am using Spire R14 v1.7.12.4

Every time I update my component for simple "visual change".. I need to re-download my container(s) before I can push the changes.  And it's literally 5 minute of sitting there waiting to download the VF page.  I will try to get you a bug report.

I submitted a bug, though i don't really think this is a bug, as you stated that this is expected behavior when you said below...

kate.dulko, on Feb 27, 2017 - 02:34 PM, said:

VF pages are included to the build process and are recompiled after you have changed the VF component as dependent files. The IDE updates the changed information for all the files.

After this, the 'Last Modification Date' for VF pages is changed on Salesforce while it stays the same as previously in the sfproj file related to your TWS project. This is why the pull is required for these files - to get the latest information from your Organization. Please pull your VF pages and continue your working process on them

 Like I said.. this means 5-10 minutes per VF component change (and that is only for a single VF page. it will be longer for multiple pages using the same component)

Hi,

Thank you for your response and for the bug report which you have sent.

We have received it and our developers will investigate it. I will contact you when we will have any results for this investigation (the nearest time).

Also, in addition to the information which I've described in one of the previous posts, our developers worked on the issue in one of the latest version of the IDE and they added the check for Visualforce pages in the case if a component file was changed. As a result, if any page uses this component file, this page is included to the build and the information its 'Last Modification Date' is updated on Salesforce as well in the IDE.

I will contact you soon with the result of our investigation for this or when we will find a workaround for the issue you are faced with.

Regards,

Kate

Hi Belacyrf,

According to your log file, the pull for the Visualforce page is required because pulling of the updated data for this page right after its build to your Salesforce Org was failed due to the time-out.

In general, the process is the next: when you change a component file, the IDE checks which page(s) use this component and add this page(s) to the build. When all the files are updated on Salesforce, the 'Last Modification Date' value is changed for them on your Org and this is why the IDE requires pulling this data from the Org to keep files in your TWS project on the same state as they are on the Org. This pull is automatically.

In the case which you are faced with, this pull fails because Salesforce doesn't return the data for a long time.

In one of the nearest versions of the Welkin Suite IDE, we will implement a possibility to configure the time-out value for TWS processes manually and you could increase it to avoid the required pull the second time.

Regards,

Kate

I am having this problem also.  I am working on a VF page with several VF components on it.  When I edit a component, it tells me I have to pull the page from SalesForce when I try to build.  So I pull the page.  It supposedly pulls it and I try to build again.  And it tells me again I have to pull the page.  So I can no longer build my project at all, it just keeps asking me to pull the page from SalesForce over and over again.  I have tried restarting TWS and it does the same thing.

What can I do to resolve this?

Lisa

Hi lryan,

Thank you for contacting us with this issue. We're preparing our fix to be released soon (looking forward to release this week). For now I can suggest you a workaround to pull changes from Salesforce after each build, that involves Visualforce pages or components - this is not so comfortable, however before we test and publish a release with fix this should allow you to build your changes.

Please sorry for the inconvenience caused.

Thank you,

Vladimir