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.*** 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. ![]() This is Source Tree 2.5.5.0.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. The third and final issue is that not all projects are displaying for me when I go to "Remote" and view the list of projects.Īnyone have any advice on what my issue might be or how to solve it? I've tried deleting all the credential entries in Windows Credential Manager. ![]() More Details: "Command: git -c diff.mnemonicprefix=false -c core.quotepath=false ls-remote fatal: ArgumentException encountered.Īn item with the same key has already been added.įatal: Authentication failed for URI path is 100% correct, and it does not matter if I go to a project and choose clone, or go to the stash site and copy the URL or click on the application hyperlink to open in Source Tree. Repository Type: This is not a valid source path / URL What's more is, even immediately after doing so, I get this error when trying to pull down a repo: Then I get a green check mark by my account info for a short period before the issue re-appears. I constantly have to re-enter my password in the account settings, after going to the stash login page to clear the captcha. ![]() Then I had to change my password due to 90 day expiration and things started messing up. After originally setting up Source Tree to connect to our Bitbucket repository server, everything was working fine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |