Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Sourcetree 3.3.6 not updating UI content properly


All was working fine, but recently had to re-image work computer.

The files inside Sourcetree are not updating properly (Windows 10, installed by another user that has admin priv - I don't have admin priv)

In the following two scenarios i am getting the issue that file list is not updating:

* if I try to switch branches or create a new branch .. the UI will not update to indicate that I have picked a new branch (i.e. the new branch will not be bolded)

* if stage files or stage hunk the 'staged files' box in the 'file status' tab does not show the staged files

In both of the above scenarios if I simply restart Sourcetree then on re-open the files/branches are updated accordingly


Any tips on how I can fix this annoying and incorrect UI situation?

35 answers

2 accepted

49 votes
Answer accepted

I'm experiencing the same thing.  Pressing F5 after fetching, making edits, etc. to refresh updates the UI.  Annoying, but usable until fixed.

Same issue after updating to 3.3.6. Didn't know about F5 though, I would always close and open it back up again in order to refresh. Thanks for the tip.

Like # people like this

Same issue here too, pressing F5 resolved any UI issues, cheers!

The F5 workaround worked for me as well. As mentioned in some other issues (e.g. #34111) removing and recreating the bookmarks or re-opening the tab can also help, but is still a workaround as I find it can reoccur at some point.

I wouldn't call it useable. 

Way to easy to get out of sync, forget to F5 and wind up in a bad state.


See the workaround I posted below.

Like # people like this

@Chris WeberAgree. Switching to another branch and immediately pulling/pushing without pressing F5 has high probably of getting/manipulating wrong remote branch.

37 votes
Answer accepted

Please "upvote" (+1) the reported bug here: by clicking as "Affected customer" in the "People" section on the right. Thanks.

Thanks, I also upvoted for the Windows version.

Like # people like this

Is it no longer possible to upvote on this bug?

Possible, spot the option near upper right corner. Field: Affected customers

Workaround from another thread on this issue:


1. Close your repository in SourceTree (click X on your repository tab)
*** If you only have one repository open, just open a new tab (click +) and then try closing your actual repository again.

2. Open your repository.


This worked for me.

Worked for me too. Thanks for sharing!

Worked like magic. Thanks a lot.

Worked for me as well. Definitely was annoying and took me a bit to even realize what was going on.

Thanks, this worked!

worked for me too! thanks for sharing

Nice it's working

Thanks, this also worked for me.

Thanks for sharing!

Works for me too.

Pressing F5 works as well

Great easy fix!! Thanks!! :D

You have to do this each time you restart SourceTree, right?

It works, thanks

works perfectly fine for me. Hope the issue gets solved soon still.

That was really messing with my workflow. Thank you for the solution! 

Worked, thanks! Hope it will be fixed anyhow.


It works untill i have to restart sourcetree, theni have to follow all the steps again.

Works for me too.  Thanks!

Works for me in 3.38 - thanks, @Chris Weber !

It works, for mee too! thanks

Same for me, this patch completely broke my SourceTree. I reinstalled (deleted all old config files) and it worked for an hour or so, then it changed its behaviour back to your desription. Please, Atlassian, fix!

Yes, I'm seeing exactly the same although I believe I have full admin privileges on my Windows 10 machine.

Looks like they released a special version 3.3.8 that's supposed to fix the issue:


From the ticket:

The SourceTree_3.3.8 is released and solves the Refresh issue (F5).
Changes link: 

SourceTree 3.3.8 [20 Jan 2020]
Fixed file list not refreshing in first re-opened tab
Fixed crash when double clicking file
Fixed duplicate file appearing when checking a file

Download link: 

Same issue and not sure if it is the reason I am seeing other issues that are making 3.3.6 unusable.  I have unknowingly committed changes to the wrong branch and ended up with merge issues in main.

Removing the bookmark (tab) of the repository and opening it again solved this problem for me, but up until closing SourceTree - the bug comes back.

Instead of +1 replies it would be better to make sure you `Like` the original question or reply to an existing solution and save the answers section for actual solutions. The email spam will become unbearable for those of us watching the issue.

Just updated to 3.3.6 a day ago.  Went from a working version 3.3.4 and updated using the automatic update feature within the app

Any operation such as switching branches, staging files, committing files requires F5 to be pressed to have the UI update/catch up.

I've read, whilst researching this issue, that it may be related to Nvidia Quadro graphics cards.  However, this machine has an Nvidia GeForce 2070 Super with the latest drivers installed.

Doesn't appear to be graphics related though - more the app not refreshing itself at all after an operation with the new version.  Switching back to 3.3.4 brings back the correct behaviour.

Give me a message if you need a video example of behaviour.


Sourcetree Version 3.3.6

Windows Version 10.0.18363.535

Same. Extremely annoying...

Yep, same here. 3.3.6 rendered Sourcetree basically nonfunctional for me on Windows 10. I'm using the most recent git version 2.25 (released ~1 day ago, which might have something to do with it) installed on my system. Installing the previous Sourcetree release (3.3.4, fixes everything, but this version seems to have no option to turn off automatic updates, so I keep reopening Sourcetree to find that it has broken itself and updated to 3.3.6, which DOES have an update tab in the options menu where you can (potentially) disable updates *eyeroll*

I have the same issue. This update is buggy.

The problem is fixed - for me at least - in version 3.3.8 but that version appears to only be accessible via the links towards the end on this post:

It's end of April now - having to press F5 after literally every action is getting tiresome. Any hope of an update? : same issue

please fix it!

+2 people
Attassian please fix it!

+ the same problem

Same. Rolled back to 3.2.6 using the provided link in the comments:

I'm having the same issue in 3.3.7.

Same, any fix ?

I have the same problem + Terminal wont start

Upgraded Sourcetree to 3.3.6 this week and experiencing the same issue.

Have reverted back to an older version until this is fixed, as having the UI reflect the correct branch is critically important.


Thanks in advance.

Is reverting a straightforward process?

I figured it out...

Like Krisztián Balla likes this

@Bill OLearyThanks for the link. I deinstalled 3.3.6 and setup 3.3.4 again, until this bug is fixed. 3.3.6 does not show up as an update in 3.3.4 now. Maybe Atlassian is already aware of this bug. As far as I can see there has been no reaction from them concerning this issue. Quite disappointing.

same here

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events