After updating a Bitbucket Cloud account in Sourcetree from an App Password to an API token, Sourcetree may continue using cached App Password credentials for existing repositories.

The account is successfully configured with the API token under Settings → Accounts, but push, pull, fetch, or clone operations may still show App Password deprecation warnings or authentication failures.

Expected result
Sourcetree should use the configured API token for all repositories associated with the Bitbucket Cloud account.

Actual result
Existing repositories may continue using outdated credentials stored in Keychain or Credential Manager. Some users report that manually updating repository remotes works, but this is not practical for users with many repositories.

This may be a regression or incomplete fix related to SRCTREE-8218 – API tokens are not compatible with Sourcetree.

Community discussion

• https://community.atlassian.com/forums/Sourcetree-questions/app-password-warnings-after-updating-Bitbucket-account-in/qaq-p/3252148