You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Just yesterday I thought it's a good day to install the latest version of SourceTree. Fortunately I didn't listen to the message popping up on startup that I should uninstall my older versions...
The reason for this is that the spinner on the left-hand side where there should be a tree view of the current repo is never finishing spinning. This happens on a quite big repo (current size: 1.86GB; due to binaries being stored in there; something we wanna change in the future but didn't have time for just yet). Smaller repos seem to work fine.
Can anyone suggest a workaround to get it going? For now im falling back to version 1.9. But since there has been issued a security advisory by Atlassian I would like to update to the latest version ASAP.
What I've tried so far is to clean out the C:\Users\%USER%\AppData\Local\Atlassian\SourceTree folder but there was no improvement achieved with that.
It seems I can't post anything stating the problem still persists. I keep getting the "You may have recently posted the same thing elsewhere on the community. Update your text, or wait before reposting." message. I have changed this post for several times until success.
It seems the workaround is the definitive solution after all. What a great support team you guys have.
Hi Marcel, there was another user with a similar issue, he removed his repo from SourceTree and cloned it again and it started working. You can see his response here.
Did this work for you?
That is merely a workaround - and not a good one I have to say. I have local branches that I cannot throw away just like that. Also my stashes will be lost. This is rather a last resort thing. I will do so eventually if I'm forced to. Nevertheless I would highly appreciate if you could pass this problem on to the developer team so they can look into it so that bug can be fixed in future releases.
Hi! Indeed, that was a workaround whilst the actual fix gets rolled out. I already informed the developers about it, as I mentioned in the other thread :)