It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Sourcetree crashes when checking out remote branch.

Two things happen when I try to check out a remote branch from my bitbucket repository.

  1. Sourcetree cannot see the local repo for this remote repo and asks me to create a new one.
  2. If it was able to see local repo for this remote repo, when it goes to checkout the branch it crashes immediately. 

Also there is a red "!" symbol by the remote icon in Sourcetree, and when I go in and edit the settings of the repo that goes away. However I am still unable to checkout remote branches and it crashes when I try.

I can fetch, pull, and push to the repo and am getting updates when I need to pull even though I can't checkout a remote branch. I can create a new local on and push it to Bitbucket, but any new remote branches I cannot checkout.

The only way I was able to checkout a remote branch was to either use the git command line, or uninstalling Sourcetree and installing version of Sourcetree from the website. Once installed I get a notifiation to update to the most current version and if I do that I am unable to checkout remote branches.

So I am unable to update Sourcetree cause it will break my remote repo. Has anyone else had this problem?

7 answers

I have had the same issue with 3.3.4 today.

I've had these problem too since upgrading to 3.3.4

I have the "!" symbol too and have to edit the settings before I can checkout. The setting changes aren't persisted so I have to do it every time I start SourceTree - crash or no crash.
I can check out by branching the "remotes" tree and selecting "checkout", but if I use Respository->Checkout or if I "Check out in SourceTree" via Stash I get the crash immediately.

I am getting exactly the same issue with 3.3.4.

Same Issue here.
Even in 3.3.8.

0 votes
mprodan2 I'm New Here May 04, 2020

are there any updates on this? 

Same issue on 3.3.8. Did not have this issue on my previous version, but frankly i am not sure which one was it :)

I've had this same issue with 3.3.9. Rolled back to 3.2.6 which seems to work

For info: I have stayed with 3.2.6, which is working OK for me (fingers crossed), for that same reason.

Like Rob Richardson likes this

Isn't it disappointing how an error like this can persist, seemingly without any action from Altlassian? At least there is hope on our side - moving to GitHub soon, which means goodbye to SourceTree. 

0 votes

Same issue here with 3.3.9.

Event viewer shows pretty much an identical error to that explained here :

Reverted to 3.2.6 and all is well.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Sourcetree

Sourcetree for Windows - CVE-2019-11582 - Remote Code Execution vulnerability

A vulnerability has been published today in regards to Sourcetree for Windows.  The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...

4,935 views 0 12
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you