#SOURCETREE WINDOWS 10 DOWNLOAD INSTALL#
#SOURCETREE WINDOWS 10 DOWNLOAD UPDATE#

Start SourceTree and reenter the correct passwords of your accounts when prompted.Remove all git or SourceTree related credentials (everything starting with 'git:' or something similar to 'source-tree-rest:' (don't have this one anymore to look it up)).Remove all Accounts under Tools -> Options -> Authentication.This issue was driving me nuts for months.

#SOURCETREE WINDOWS 10 DOWNLOAD UPDATE#

Kris's solution also works if you only want to update Git Credential Manager for Windows specifically, though does require config changes.

#SOURCETREE WINDOWS 10 DOWNLOAD INSTALL#

Until Atlassian update their embedded version, you could install Git for Windows 2.14.0 and within SourceTree, click 'Use System Git' in Options. The latest Git Credential Manager for Windows is included in the latest Git for Windows. The latest version (1.12.0) released a couple days ago fixed the remaining issues I had with Bitbucket authentication. The majority of issues in Git Credential Manager for Windows have been fixed in recent versions.

After updating SourceTree, go to Tools > Options > Git and click 'Update Embedded Git' to get the latest version (at least 2.14.1). I've not seen the issue occur for non-Bitbucket accounts.ĮDIT (): The embedded Git has now been updated, alongside the release of Sourcetree 2.1.11.0. Currently, logging in with your username is still accepted but seems to cause several issues ranging from this repeated login prompt issue to the 'too many login attempts' error when pushing. Why doesn't push (or pull) use that same method to authenticate?ĮDIT (20 June 2018): Recent changes to Bitbucket authentication has also meant that you must use your email (NOT your username) when logging in.

It seems weird, since I have OAuth for both accounts, and can browse my repos (some of which are private) with no problem. The push was successful, and I saw also that a new entry in 'Saved passwords' was created for that repo. That forced the GCM dialog, to which I supplied credentials for the repo that I was pushing to. I removed the Saved passwords that were stored and re-tried a push. Tools > Options > Authentication seemed also to be helpful for me. I agree the GUI is borked since we have no idea for which account or which operation the credintial manager is asking this information. I have had Source Tree 2.x for a long time and don't recall this headache. The problem seemed to start for me when I added a new bitbucket account (academic) and wanted to use two accounts. I thought I had got the spontaneous dialogs to go away, but they do sometimes re-appear. The commands above seemed to help, but not right away.

Sourcetree windows 10 download