We are currently unable to use the service because the Save function for the API token is not working.
Current environment:
macOS: 26.5.1 (25F80)
SourceTree: 4.2.18
If API token authentication is not currently supported, please provide a way to use the previous OAuth authentication method as an alternative.
Hi everyone,
Someone finally mentioned me with a solution that resolved the issue!
Please check the link below—I hope it helps you resolve this issue as well.
Thank you to everyone who took the time to reply and help along the way!
Hi @허지수 ,
We've talked about this here https://community.atlassian.com/forums/Sourcetree-questions/Sourcetree-for-Mac-v4-2-17-quot-Save-quot-button-is-disabled/qaq-p/3242900 (I mean, you're the author)
Have you tried re-creating this API token and also, does this API token have scopes? Can you maybe share the steps you've taken to create it?
Potentially, Pratap Guvvala can share some additional insights apart from those shared in linked discussion 👀
Cheers,
Tobi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here are the steps I followed to create the API token with the required scopes:
1. I went to https://id.atlassian.com/manage-profile/security/api-tokens.
2. I set the expiration date to December 31, 2026.
3. I selected the **Bitbucket** app.
4. I granted all available **Bitbucket** permissions.
5. I generated the token.
However, when I enter the token into Sourcetree, the button is still disabled.
At this point, I suspect there may be a compatibility issue with a specific version. The strange part is that everything works correctly on Windows—the credentials can be saved without any issues.
Since the problem persists even after updating macOS, could this be caused by a missing component in the installation or a permissions issue on macOS?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since the problem persists even after updating macOS, could this be caused by a missing component in the installation or a permissions issue on macOS?
@허지수 might just be. It would be great if I had Mac to potentially help you troubleshoot this, but I'm mainly working on Windows and I'm not familiar with Apple OS that much 🫤
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @허지수
With all the suggestions, is this still an issue for you?
If no, please accept one of the answers so that everyone is aware that this has been resolved. 🙂
Thanks,
Anwesha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi, @Anwesha Pan
I tried all of the suggestions you provided, but unfortunately the issue still hasn't been resolved.
Thank you for taking the time to look into this and for your help. I really appreciate it.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.