Sourcetree asking for password again and again

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?

4 answers

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.

 

Scott

It's working

Thanks

Can you please include a screenshot and describe what host you are trying to connect, protocol for the remote URL and if you also have an account added in Sourcetree?

Thanks!

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.

 

Thanks :)

 

Captura de pantalla 2018-01-16 a las 15.00.01.png

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,

  1. Remove account in Sourcetree
  2. Remove all keychain items added by Sourcetree
  3. Restart Mac 
  4. Add the accounts back in Sourcetree 
  5. Make sure to enter password and click "Always Allow" when keychain prompt is displayed for the new keychain items. 

Let me know if this helps!

Thanks for the answer, but it didn't work. 

It makes my computer unusable. If I have source tree running in background I get those annoying prompts asking me for the password again and again, whatever is the app I am using in the foreground. 

Even after I deleted that account from SourceTree, it is asking me for the password all the time. 

This same thing happens to me after updating to 2.7 (152).  I'm on OS X El Capitan, everything was fine prior to this update.  This now causes my Bitbucket server to require a CAPTCHA frequently.  Can't use Sourcetree until it's fixed.

@Manuel García-Estañ@Michael Spears

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 deleted all the items in my keychain related with source tree and added the accounts back. Then some items are added into the backlog again. Still, a few mins later I see all those prompt again. 

Deleting the items in my keychain didn't work, I'm still being asked for my password.  I did try a git fetch from sourcetree, this was the error:

Something went wrong. one or more parameters required to renew token is nil

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.

That link you provided doesn't work.

Going back to 2.6.3 fixed my problem.

I've corrected the link.

Thanks!

@Manjunath Basaralu Srinivasa the displayed link is correct, but if you click it there's a malformed Google Analytics link behind it.

 

I have the same issue with SourceTree as @Manuel García-Estañ and @Michael Spears describe. I will briefly tried out the beta, but also ended up reverting to 2.6.3.

SourceTree Archive: https://www.sourcetreeapp.com/download-archives

@Manjunath Basaralu Srinivasa I think there's a trailing dot after the `.zip` extension that breaks the link.

 

`.zip.` instead of `.zip`

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. 

Hello @Manjunath Basaralu Srinivasa

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

Hi @Roland Heusser

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. 

Thanks!

Happy hunting for the cause 😉

Did anyone find a good solution to this? I am using OSX Sierra 10.12.6 and Sourcetree 2.6.3 and am encountering this problem repeatedly as well.

Maybe a clue - everything was working fine until I installed Git 2.1.62. I reverted, alas the problem remains. Instructed Sourcetree to use System Git. No dice.  

Took a deeper look and was able to solve the issue with the info here: https://developer.apple.com/library/content/technotes/tn2449/_index.html

Restarted, back to normal

0 vote

Same thing happens to me.  Tried everything here to no avail.  Delete 2.7.1 and redownloaded 2.6.3 and I am back in business.  Good job 2.7.1.

Hi All,

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.

 

Thanks,
Manjunath
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)Screen Shot 2018-07-03 at 11.43.56 PM.png

Hi,

I have solved by changing configuration :

Preferences -> Git tab -> Select 'Use System Git'

 

Thanks!

that doesn't work for me.  (version  2.7.6.  )

Can you please remove the account if its added in Sourcetree, remove any remnant keychain items for GitHub and add the account again and see if that works?

That still does not work.

I also tried deleting the other github keys in keychain (used by other apps).

 

This is new for me in this version.  Previous versions did not have this issue.

I should be clear though, the password it is asking for is the passphase on my private ssh id_rsa.  This didn't used to be a problem though....   is there something else I need to do so this works?

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

ssh-add -l 

To load keys, use this command

ssh-add <path_to_key> 

e.g.,

ssh-add ~/.ssh/id_rsa 

 

Thank you Manjunath,

 

I did verify with `ssh-add -l` that the key is loaded.  I also added the key again as described.

 

However the issue remains the same in asking me for the key (shared secret) with every push/pull/etc.

Alternately, can you try using HTTPS authentication? 

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 30, 2018 in Sourcetree

Tip from the team: configuring Git or Mercurial in Sourcetree

Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...

570 views 1 2
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you