app password warnings after updating Bitbucket account in SourceTree to use an API token

[TomCatchesides]

I'm using SourceTree 4.2.18 on macOS.

Following the warnings about app passwords being deprecated, I've created an API token and edited my Bitbucket account within SourceTree to use the API token (following these instructions). All of my repositories are within this single Bitbucket account and I don't have any other accounts set up in SourceTree.

When I try to push a commit from SourceTree to my git repositories on Bitbucket, I'm still getting periodic "CHANGE-3222 - Functionality has been deprecated" errors. I get the same error if I try to clone one of my remote repositories.

How do I go about making SourceTree work with API tokens?

[lcapozzi]

Found a workaround. Manually editing the remote and changing it to:
git@bitbucket.org:{username}/{repo}.git works without any issues. Now I only have to update around 100 entries...

[TomCatchesides]

I'm glad you've got yours working!

The remote URLs I have in SourceTree are of the form https://{username}@Bitbucket.org/{username}/{repo}.git so are you saying that I should change that to https://git@bitbucket.org/{username}/{repo}.git ?

If so, that doesn't work for me: I get this password dialog and authentication errors.

[lcapozzi]

remove https://. It should start with git@bitbucket.org.

[TomCatchesides]

Thanks, @lcapozzi 

git@bitbucket.org/{username}/{repo}.git is giving me the following error (although obviously with my values for username and repo name):

fatal: 'git@bitbucket.org/{username}/{repo}.git' does not appear to be a git repository

fatal: Could not read from remote repository.

[lcapozzi]

I worked on our repos all day and right now, all of a sudden, the git@bitbucket.org method is not working any longer. It say I don't have permissions. WTF?

git@bitbucket.org: Permission denied (publickey).

This must be a joke

EDIT: That's not even working using other clients (Fork), so maybe this endpoint has been blocked today? Can Atlassian give some answer?

Speaking about answers... I also issued a ticket for this issue and I've been replied that (As a paid customer) my level of support is the community. Congratulations. 

[Tomislav Tobijas]

@Ben can you, or maybe someone else from the Bitbucket team, provide some insights here? (or potentially create a ticket) 👀

[lcapozzi]

Update: after being able to, at least, see my remote repo list I tried swapping the current repo's remote while selecting it again from the list and now it seems to be working. Hopefully it'll last, so I won't have to manually change over 100 repos 

[TomCatchesides]

Well done, @lcapozzi 

Can I ask what your steps to resolve this were in the end? And is the solution working during one of the scheduled brownout periods?

[lcapozzi]

- Removed all stored credentials and ssh keys

- Removed the account

- Remade the account with the API token

- Open any repo and do any git operation. It'll prompt for a password

- Type your Bitbucket account password

- Edit the origin and click on the hosted projects, so a list of remote repos will pop out

- Select your repo and save

[lcapozzi]

We have the same issue. We've been force to move to API Tokens, but the SourceTree client is not working any longer on some machines. With the same API Token and same credentials we don't have the same results. If we switch to another client (for example, Fork) everything works as expected. We cleared the stored Keychain entries, but that hasn't helped. We are basically locked out our entire codebase. Please, fix this asap!

[TomCatchesides]

@lcapozzi I'm glad I'm not the only one, but you'd expect Sourcetree to work with Atlassian's mandated changes wouldn't you?

[lcapozzi]

absolutely. Considering that I'm also on a paid account, it's utter nonsense that I'm unable to chat with a human being via the support page. I'm seriously considering migration to another platform. 

[Tomislav Tobijas]

Hey @TomCatchesides ,

Have you tried clearing the macOS keychain? It should be something like Keychain Access 👀
I don't have Mac, but I know that a similar thing sometimes needs to be done on Windows in Credential Manager. 

In Mac, it's something like:

1. Open Keychain Access on your Mac.

2. Search for bitbucket.org.

3. Delete any entries related to your Bitbucket account.

4. Restart Sourcetree and perform a Git action; it should prompt you for your credentials, where you can enter your email and API token

Potentially Sourcetree cached old credentials in the local repo config. You could open repo in Sourcetree > Settings (top right) > Remotes and check the origin remote. (select 'edit')

Cheers,
Tobi

[TomCatchesides]

Thanks for the suggestion @Tomislav Tobijas! I've tried what you've suggested and got SourceTree into even more of a mess now…

1. Deleted Bitbucket entries from KeyChain access.
2. Relaunched SourceTree.
3. Edit account: the API token has been cleared, so I reenter it and click Save.
4. A dialog window appears, asking for a password (see first screenshot). I enter my Bitbucket account password.
5. When I try to pull from one of the remotes in this account, I'm asked for a password again (second screenshot). I've tried entering my account password or the API token and in both cases I get the following error:
   

   remote: You may not have access to this repository or it no longer exists in this workspace. If you think this repository exists and you have access, make sure you are authenticated.
   
   fatal: Authentication failed for 'https://bitbucket.org/…/'

Editing the account and changing back to basic auth with the app password that I was previously using resolves this, but that is of course going away soon.

[lcapozzi]

I'm on the same identical situation. I've also cleared the stored SSH credentials... everything. 

[Tiago_Lira]

Having the same issue. 
Changed bitbucket auth to use API token, sourceTree still gives me the same "App Passwords" error.

[TomCatchesides]

@Tiago_Lira Yeah, there seem to be a few of us affected by this. I hope that we find a solution before I'm forced to move to a new host for my repositories.