SourceTree UI is constantly out of date

Question

Recently SourceTree is not updating the UI properly, either in the files list for a particular repo or in the Repository Browser.

When looking at a repository the list of modified files does not update - I have to switch to different views (eg click on different branches and/or History/File status/etc) in order to get the list of modified files to update.  Obviously I need the list to update in order to be able to add my changes to the Git index and make the commit.

But then once I commit changes in my repo and switch branches, the Repository Browser still says that I have uncommitted changes and am on the old branch.

To illustrate my point, take a look at this screenshot - the window on the left is the Repository Browser and you can see that it thinks the current branch is "advanced-templates2" and that there are 45 modified files; but the repository itself has just had all the files committed and been switched to the master branch.  This screenshot was taken quite some time after the commit.

This behaviour has only started with a recent update.

All my repos are Git repos, I am running SourceTree 2.6.3(134) on Mac OS 10.13.1

unknown · Answer

I agree. Windows 10, version 3.3.6.

Constantly have to hit F5 to make sure that my UI is up-to-date, this should happen automatically!

ghache1 · Answer

I have the same issue with release 3.3.6 on windows 10.  Seems like everything I do need an "F5" (refresh) to be done after or nothing updates.  Pretty much each time I click somewhere I need to do F5 after.  Commit a file...still shows as not committed.  Hit F5 it shows fine then.  Download changes of a repos...need F5 after to see the changes.  I tried going back to the previous release...but I guess something stayed behind since it does the same thing now :-(

I agree that it is totally annoying and make it unreliable to be used correctly.

erichfrazer · Answer

I agree. I have exactly the same issue. It's always out of date, and the way it's dealing with files and checking them in and out seems suspicious... I've had 3 checkins go wrong so far where it says, "the commit happened but the push was unable to complete", but in actuality the commit did NOT happen and the files were lost. And it's not keeping the changed files accurate that's for sure. I've had to switch to GitKraken for now. I hope you fix it soon since your UI is the cleanest I've seen so far and like it.