You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Since last update (2.7 152), source tree ask for my username and password every few seconds (around 30), making the app unusable. A modal window is shown in the front of the app, and it keeps appearing even if I enter the right password.
How can I solve this?
I didn't read all the comments -- if this has already been said, I apologize for the duplication.
MY assumption of what's going on here is that somehow the sourcetree internal git is fubared in some way. Let's say internal is 2.15.1 -- but my system one is 2.15.1. Somehow, they are not behaving the same with regards to at least authentication.
Again, this is an assumption here, and I will test with the next set of sourcetree updates, but I think when an update or a certain level of update for sourcetree comes out -- the setting for which git to use gets cleared or (re)set to internal git. THIS CAUSES ME ALL KINDS OF GRIEF.
In the comments here, there are posts that say that the command line git works. This is and always has been the case for me. I "resolve" the sourcetree shenanigans by going to the preferences for git and selecting to use the system git (even if it's the same version).
This has resolved the issue of sourcetree repeatedly asking me for my password and having the input of a valid password not working. I did not erase passwords in keychain, unlock keychain, save to keychain, use command line once, uninstall or re-install sourcetree -- I just changed the git to command line git (and restarted sourcetree just because).
YMMV. Good luck.
This has always been a problem and I never knew why, thank you so much. Just changing the embedded git to system resolved the issue for me straight away. I tried everything including OAuth but nothing worked and I never received a password prompt either, which was annoying since I couldn't find the setting to enable it. But just changing the git to System fixed all issues. Thank you for saving hours worth of work.
What ended up working for me, using OAuth on Mac w/ Sourcetree v4, was to find my github-related credentials in the Keychain Access list, deleting them, restarting the OS. Recreating the github credentials with Sourcetree, granting Sourcetree access with the "always allow" option when prompted, and then verifying by clicking on the github credential that Sourcetree had access to it.
It seems that there can be a different cause for the issue.
I'm on 3.3.4, win10. After a time off, got this issue. I use ssh key to connect to gitlab and suddenly SourceTree was not able to identify a key, and kept asking annoyingly for credentials.
Solution for me was to make sure correct configuration is set, and it was:
SSH Client Configuration: "SSH key path" path where certificates are and "SSH Client" i changed to "OpenSSH".
All works fine now.
I use the Google Account as authorization and have similar problem. So it is need to refresh OAuth token.
In SourceTree navigate: Tools > Options > Authentication Tab.
Then expand your bitbucket account and select Edit.
After that press Refresh OAuth token button.
Sincere apologies for the issues you have been facing with regards to authentication on Sourcetree Mac over the last few months. Please read the response from the product manager of Sourcetree here - https://community.atlassian.com/t5/Bitbucket-questions/Authenticating-with-Bitbucket-not-possible/qaq-p/502460#M25871
Also, I have submitted an issue on JIRA - https://jira.atlassian.com/browse/SRCTREE-5600 and have been working on getting it fixed. We will hopefully have a fully functional build very soon.
Sourcetree Mac Developer
I am getting this repeatedly on 2.7.6. Very frustrating after update. By getting this, I mean when connecting for any pull or push to github using a connected github account (of which the 'connect account' process works perfectly)
Please help! Very tired of putting in my password repeatedly every push or pull. (note, my ssh key has a passphrase on it. this never used to happen with previous versions of sourcetree)
There are some changes in the OpenSSH on macOS that causes these issues. More details can be found in Apple's Technical Note - https://developer.apple.com/library/content/technotes/tn2449/_index.html
Every time you restart the Mac, check if the keys are loaded to the agent and if not, load them manually. This would just work fine with Sourcetree.
To check if key is loaded, use this command
To load keys, use this command
Here is an screenshot. You can see three modal windows. The three are asking for the same password. These modals appears randomly every few seconds.
It is asking the password for an account which I defined in the sourcetree accounts, but it is not even the account owner of any of the repos which I am managing at this moment. I don't think it is related, but the repo url protocol is https. And the host is bitbucket.
This seems to happen on macOS High Sierra when you have for some reason denied access to a keychain item to Sourcetree and we cannot read keychain items. Here are a few things that got the issue resolved for me personally,
Let me know if this helps!
Sourcetree tries to check if there are commits that needs to be pulled for you in the background and hence you see the prompts when the account isn't available. As I mentioned, please add the account back and confirm that sourcetree has written to keychain to make sure this works for you. If for some reason, you don't see keychain items after saving the account, please restart your mac once.
Should you have more trouble, I'm happy to work with you personally to get these issues resolved. Happy to help anytime. Thanks for your patience.
I recommend you to try out our 2.7.1 beta which has potential fixes around authentication and provide feedback. You can download the beta here - https://bitbucket.org/atlassianlabs/sourcetree-betas/downloads/OSX_Beta_Latest.zip
To providing feedback, please file tickets in https://jira.atlassian.com/browse/SRCTREE whenever you hit a problem and make sure to add the “trusted_tester” label so we can investigate ASAP.
@Manju the displayed link is correct, but if you click it there's a malformed Google Analytics link behind it.
SourceTree Archive: https://www.sourcetreeapp.com/download-archives
I've corrected the link.
The password prompt would come up only if Sourcetree can't find a saved password.
Can you delete files with the format <username>@STAuth-<host> under ~/Library/Application Support/SourceTree/ and add the account once again to see if this helps?
When you add the account, it should write the file back to app support folder. If not, there is some permission issue accessing keychain at which point I would recommend a restart of mac to see if the permissions are corrected.
Thanks for your response.
In one of my debugging attempts I removed SourceTree completely with AppCleaner, which deletes the Application Support folder as well. I also deleted all keychain entries that were related to SourceTree.
The only thing I didn't do was rebooting the Mac or I am not certain anymore.
Since 2.6.3 is working fine for me and the problem only occurs with the newer versions, I will keep using the old ones for now.
Also – not sure if Apple changed anything related to the keychain in High Sierra, but I am still using Sierra (10.12.6).
After restart, did you check if the ssh keys are loaded to the agent?
Apple changed a lot of stuff related to ssh in 10.12. You can read the note here - https://developer.apple.com/library/content/technotes/tn2449/_index.html
This is the primary reason why ssh breaks for all users whenever they restart the mac. The note also has some tips to load the keys automatically but that hasn't worked for e personally. You can give it a try yourself and see if it works for you.
However, what surprises me is the fact that this happens with 2.7 only while there isn't any real change in the ssh key handling for 2.6.3 and 2.7 versions of Sourcetree. I'm on it to figure out why this happens.