Since updating to 2.7.0 SourceTree is basically broken for me.
It constantly asks for my credentials; apparently it does this because our self hosted BitBucket instance blocks my account after SourceTree spams too many requests to do.. something.
Once my account is blocked, the error seems to trigger the credentials dialog.
Had no problems before this version. Others seem to also be experiencing issues:
Came across this same issue and multiple posts too. So consolidated my research and fix at one place https://stackoverflow.com/a/52884626/5107365. The summary is, problem solved when I used the same password for Atlassian's account address(which is the Gmail ID I used to OAuth to my bitbucket user), like that of my Gmail ID.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have since found out that the issue only occurs if I use repositories with https authentication. I switched everything over to ssh, and then it just works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Team members are employees working across the company in a wide variety of roles.
January 24, 2018 edited
Have you added your account in Sourcetree? If yes, can you please confirm if the protocol associated with the account is same as the remote URL of your cloned repository?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.