The SourceTree application shows that I am logged in correctly, yet it won't let me perform a pull.

[Jorge Ortiz García]

Hello,

The SourceTree application shows that I am logged in correctly, yet it won't let me perform a pull. This issue appeared overnight. I have tried logging out and back in, removing and re-adding Windows credentials, and even changing my password. Despite showing that I am successfully logged in, the app won't allow me to perform a pull or any other operation.

Thanks

[Tomislav Tobijas · Accepted solution]

Hey @Jorge Ortiz García ,

Are you on Windows or on Mac? Also, which version of the app (Sourcetree) are you using?
If you're not using the latest one, can you try upgrading it?

Also, are you seeing any specific message when you're trying to perform a pull?

This could be something related to desynchronization, so I'd advise clearning credential manager and things within Sourcetree (Tools > Options > Authentication (on Windows)) 👀

Cheers,
Tobi

[Jorge Ortiz García]

Hello,

I have the latest version. Manually deleting the files fixed the problem after a clean install.

Thanks

[Reuben Jackson]

I am having the same issue. I have cleared all the credentials in Source Tree, and in the windows credential manager. I have created an API token with all 46 scopes enabled just to be sure. I have added the API token into source tree, and authentication is confirmed. 

The error i get when doing a pull or fetch:  

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.....

I have not changed any other settings. The repository address is good. It is the same as the web URL

Feeling really anoyed. I have wasted several hours on this issue. Going in circles. 

[Jorge Ortiz García]

Hello,

That’s the exact error I was getting. Try locating the SourceTree installation path and deleting everything manually, since uninstalling doesn't work. Then, it works when you reinstall it.

Thanks

[Reuben Jackson]

I got there in the end. I had deleted the passwd file and credentials multiple times... but i think the subtle trick was closing the app prior to deleting the passwd file below... I'm sure i did previously. AI generated Instructions below

• Close SourceTree completely.
• Press Win + R on your keyboard to open the Run dialog.
• Type %localappdata%\Atlassian\SourceTree and press Enter.
• Look for the file named passwd and Delete it.
• (Optional) If you see a file named userhosts in that same folder, you can delete it as well to clear out stuck usernames.

[Gabriela]

Hi @Jorge Ortiz García, welcome to the community. This is the app password deprecation, not a real login problem. Bitbucket Cloud is running scheduled brownouts through 27 July and removes app passwords entirely on 28 July, so SourceTree still shows you connected while the pull fails. Changing your password or re-saving the Windows credential won't fix it. Create an API token at Account settings > Security > Create API token with scopes (tick read:repository and write:repository), then edit the account in SourceTree and use your Bitbucket username with that token in place of the password. Full notice here: Bitbucket app password brownout.

[Jorge Ortiz García]

Hello,

I’ve tried logging in using an API token, but that doesn't work either. I created the access key, but I’m still getting an authentication error.

Thanks

[Gabriela]

The token type is almost certainly it, @Jorge Ortiz Garcia. A plain API token is rejected for Git — it has to be an API token with scopes. Create it at Atlassian account settings > Security > Create and manage API tokens > Create API token with scopes, pick Bitbucket as the app, and tick read:repository and write:repository. Then in SourceTree use your exact Bitbucket username as the username (case-sensitive, from your Settings page — not your Atlassian email) and paste the token as the password. https://support.atlassian.com/bitbucket-cloud/docs/using-api-tokens/

[Jorge Ortiz García]

Hello,

What you're suggesting doesn't work. I finally fixed it by manually deleting the local SourceTree files and reinstalling it, since uninstalling alone didn't work either.

Thank

[Gabriela]

Glad you got it sorted, @Jorge Ortiz García, and thanks for coming back with what actually fixed it. That's a useful signal in itself: when a fresh token doesn't move it and a clean reinstall does, it was local SourceTree state, not the auth method. For anyone landing here later with the same "logged in but every pull fails" — if a new token doesn't help, stop chasing the credential and clear the local state (delete SourceTree's app-data files and reinstall, the way you did) instead of staying on the app-password angle.

[Gabriela]

That reinstall worked because SourceTree holds onto stale credential and remote-helper state locally. Dropping in a fresh token often won't take until that local state is gone, which is why uninstalling alone didn't do it and deleting the app files plus a reinstall did. Anyone landing here still stuck should clear the local SourceTree files before assuming it's the token or the credentials.