I have the latest version of SourceTree installed on my mac and it's crashing on the remote tab since last week. My account is connected to BitBucket using OAuth.
Before I updated to the latest version, I was trying to create a local repository and I checked the option to create a remote repository. When it got onto the remote repository options, it was crashing referencing something about owners being deprecated and the error code 2770.
I decided to update to the latest version.
When I do the same procedure, it just crashes.
When I go onto the remote tab, it also crashes.
I've tried readding my account and clearing all of my settings, but no joy.
Any ideas?
Hi Tobi,
Thanks for getting back.
I'm already connecting using SSH. I tried HTTPS, but still the same issue.
I've gone through the git related issues and none of those are relevant.
As this is now a hard crash, the only thing I really have to go off is my mac crash log which indicates:
Crashed Thread: 1 Dispatch queue: com.bitbucket.teams.requests
This seems to line up with the deprecation notice I was receiving initially before I updated SourceTree
Oh, interesting. I wasn't aware of that Bitbucket deprecation. This is what I've managed to dig out (and it's actually related to Bitbucket):
If your account was created before February 2023, you may still be using a Personal Workspace (Legacy). These workspaces use deprecated "Owner" fields that can trigger the 2770 error and crashes in newer client versions.
- Log in to Bitbucket via your browser.
- Check if you are prompted to transition to a Shared/Team Workspace.
- If you are using a legacy workspace, follow the prompts to update your Workspace ID and transition to the new model
Can you check the Bitbucket side and see how things look like there?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tomi,
That is very interesting yes, and that must be exactly what is happening!
I think I created my account close to 10 years ago now!
I'm not seeing an option to transition though. Chatgpt seems to think the only way to get this working again is create a new workspace and migrate everything over. Unfortunately, I have quite a lot of repositories and this would take a very long time.
Is there something I'm missing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tomi,
Some updates for you.
After some digging, I'm pretty sure that the workspace account we use has been upgraded as it's never been a personal one as we work in a team. Unless it's my own personal bitbucket account? It's quite difficult to find definitive information on how to check!
However, I'm pretty sure it's related to that owner field regardless! I remember that on SourceTree, when creating a local repository and checking the create remote repository, on the remote repository screen, there was always an owner field there.
Please do let me know if you need me to provide more information.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Vinnydude ,
I'm currently on TEAM '26, so I might be a bit slow to respond 👀
When it comes to Bitbucket, it might be quickest to raise a question here: Bitbucket questions
I would need to test this out as well, but I could only do so on the other PC I have at home. I mean, I could do it next week, but if you'd like to check the Bitbucket part up until that, it might be a good thing to ask the community (also, link this question)
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Vinnydude ,
Just to confirm, you're running v4.2.17 currently? (should be the latest one)
Crash might be related to how Sourcetree handles auth protocols. You could try switching your connection to SSH to see if that will help 👀
Here's the official article: Set up SSH with Sourcetree
Additionally, you could check if there are any Git-related issues Troubleshooting Bitbucket Git issues that might result in a crash.
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.