Unable to clone repo from Bitbucket

[Vlad]

Running latest version of Sourcetree 3.4.27.

1. Authentication is done using API Token. Authentication is OK.

2. All Remote repositories are displayed correctly in the Remote tab.

3. When trying to clone Repository I get CredentialHelperSelector with 3 options (no helper, wincred, manager) - tried all 3 and neither works, it just goes into loop so have to close the app.

In Bitbucket it shows App Authorization for Sourcetree and in Atlassian it shows that API token has been accessed as I try to clone the repo.

It seems there is an issue with authentication, but Authentication is OK and I can see all Repositories.

Please help, not sure what to do now to fix it.

Cheers!

[Tomislav Tobijas]

Hi @Vlad ,

Can you try the following - in Sourcetree, set your authentication type to Basic, use your Atlassian email as the username, and enter your API token as the password. On Windows, make sure to click Refresh Password before saving.
More info about that here: Add an API token to Sourcetree or another application 

If you're still stuck, what you could try is to remove any saved credentials for Bitbucket from the Windows Credential Manager, restart Sourcetree, and re-enter credentials.

If that also doesn't help, you could consider switching to SSH auth. Here's the article on how to set it up: Set up SSH with Sourcetree 👀

Cheers,
Tobi

[Tomislav Tobijas]

Also, if none of that works, can you try reverting back to 3.4.26 to see if cloning will work there (with an API token auth)?

[wandrade]

I have the same problem, tried to revert to 3.4.26 and still not working.

[Tomislav Tobijas]

@wandrade can you maybe check open issues related to this topic? You could change the search filter, but the goal is to potentially find if anything related to what you're seeing is already reported, and if someone maybe found a workaround 👀

On top of that, if there's no open bug, you could create one yourself, just add a detailed description of how to replicate the behavior. This should then land in the team backlog, and someone will probably take a look at that.