COMPLETELY REMOVE SOURCETREE WINDOWS PASSWORD

In that case, you would use your app password instead of your account password For the first two, you can still use the HTTPS protocol users experiencing this issue were most likely already using.

You can do one of the following three authentication methods to connect to your Bitbucket Cloud account. You can either utilize OAuth using HTTPS, Basic authentication using HTTPS, or Basic authentication using SSH.

Next, Add your Bitbucket Cloud account back to the connected Accounts.

Next, under Accounts remove your connected Bitbucket Cloud account credentials completely.

On the Options, window click the Authentication tab.

COMPLETELY REMOVE SOURCETREE WINDOWS UPDATE

Update to the latest version of Sourcetree for Windows.Īfter updating (or confirming you are already on the most updated version of Sourcetree for Windows), on the toolbar, click Tools, then click Options. If your issue is resolved, you can skip the following steps.

try and push/pull to the connected Bitbucket Cloud repository.

To Git remote URL using Bitbucket Cloud username:.

From Git remote URL using email address:.

In the case that the email address is used as the username in the URL, the URL will need to be adjusted like so: Please check your Git remote URL for this issue. Some Git remote URLs in Sourcetree may be using a user’s email address which could cause authentication errors.

Authentication with app passwords do not support the use of a user’s email address as the username.

***Please note, the following steps are for Sourcetree for Windows.***

COMPLETELY REMOVE SOURCETREE WINDOWS WINDOWS

So, if you are using Sourcetree for Windows and experiencing this issue please take the following steps for resolution. What is the fix (or workaround)? Windows-specific resolution

Instead, we strongly believe this issue is related to issues with how Windows Git Credential Manager is potentially caching and still using bad credentials (even after users have updated their Bitbucket account password to an app password in Sourcetree for Windows). Remote: App passwords are recommended for most use cases and can be created in your Personal settings:Īlthough this issue occurs when switching to an app password, we have determined this issue is not caused by the use of app passwords themselves. Remote: See our community post for more details: Error: remote: Bitbucket Cloud recently stopped supporting account passwords for Git authentication. push/pull from their connected Bitbucket Cloud repository) they receive the following error message indicating that they are still using their account password and need to change to using an app password. However, when users then go to execute Git operations from Sourcetree (i.e. After updating the used password to the user’s new app password, Sourcetree verifies that it was able to successfully authenticate the connected Bitbucket Cloud account (as shown below): What is the issue?Ĭurrently, the issue shows when a user goes into their connected Bitbucket Cloud account in Sourcetree for Windows and updates their password to their new app password.

We have not noticed any similar issues with Sourcetree for Mac. Please note, this issue is specific for Sourcetree for Windows. We want to take the time to discuss it and provide a workaround to resolve the issue.

COMPLETELY REMOVE SOURCETREE WINDOWS HOW TO

With the recent removal of Bitbucket Cloud account passwords for app passwords (please see our Bitbucket Cloud community post for details on why we made this change for security purposes, how to create and use app passwords, and an informative FAQ) a number of Sourcetree for Windows users have brought to our attention an issue they are experiencing.

Completely remove sourcetree windows