I got the latest version of sourcetree yesterday. (April 4th 2018) I am unable to push my code changes to remote . I see the below error. How ever I have my password set up in sourcetree for my bitbucket account.
git -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=sourcetree push -v --tags --set-upstream origin refs/heads/feature/branchName:refs/heads/feature/branchName
Pushing to https://firstname.lastname@example.org/domainName/projectname.git
fatal: could not read Password for 'https://email@example.com': Device not configured
Completed with errors, see above
I tested many of the solutions that are explained here, but finally the only that really worked for me was this (for Mac users only):
There seems to be some oddity with keychain and macOS that causes this issue. I faced the same a couple weeks back and just had to restart to my Mac to get it fixed. Give it a try and let me know If it works for you. If it doesn't, please remove the account and add it again. You can enable a debug menu from Preference window -> Advanced tab and set debug logging and enable auth logs to help us get all the logs in case of failures.
Sourcetree Mac Developer
I have tried everything you mentioned and can't get it to work again. I have the same exact issues after upgrading yesterday. I have disabled 2FA on GitHub, reset by personal access token, remove the account and added it again, remove my github keychains, reset my machine, tried basic, oAuth with SSH and HTTPS and nothing has worked. Please help I am starting to lose my mind!
With build 2.7 (159) I got this error
With build 2.7 (165) I got this error...
Device not configured
With build 2.7 (167) I get this error...
The remote service said: 'The operation couldn’t be completed. (SDNetDomain error 7.)'
I tried the archive build to 2.7 (152) and got...
Something went wrong. one or more parameters required to renew token is nil.
So command line it is!
Bug is still not fixed.
But there is a workaround: go to Sourcetree>Preferences>Accounts, select account, tap Edit and change protocol from HTTPS to SSH. You have to generate SSH key and add it in bitbucket profile settings to make it work.
The interesting thing is that everything works fine on other computer in our office, no need to change to SSH there. It uses exactly the same repository settings, but different user profile.
There is a separate thread, and somebody published working workaround:
Try change repository link format from "https://firstname.lastname@example.org" to "https://username:email@example.com"
Yes, it is not safe, but it is working!
Another thread is here:
I encountered this issue when trying to use the "finish" action on a release branch.
For some reason, the same action works for a feature branch.
I tried some of the answers above.
I tried changing my account settings to SSH. There's a button there that says "connect your account". This opens a mini browser that simply does nothing but directing you to bitbucket's login.
Only other option for you beside surfing the web is clicking cancel, which obviously not connects the account to SourceTree.
Could only connect via basic method, but this didn't change anything.
I tried some other solutions from the threads provided by other people in this thread and nothing works.
Only solution worked for me was the last thing I wanted to do, and is downgrading to 2.7.2.
And to be honest? This is the exact same version as 2.7.6 but without bugs. There's nothing new that worth that headache so just downgrade to 2.7.2.
Using Visual Studio Mac with Source Tree 3.1.2 My machine already has ssh keys, etc., for other projects on BitBucket
I had a local repo for a project that was mature enough to put in the cloud. So I created new bitbucket repo. I could not get the instructions for Visual Studio Mac to add remote repo to work, so I opened Source Tree and opened the local repo.
Then I went to Menu -> Repo Settings and then Remotes tab. I added the URL of the newly created Repo. But, here is the catch:
The URL of the page you create will be something like:
That is not correct, but SourceTree will accept that URL. And then fail (with the error in this issue) when you try to push to it..
What you actually want is:
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events