Unable to finish release with sourcetree 2.7.6

Koen Verhulst June 14, 2018

I'm having issues while trying to finish a release with sourcetree 2.7.6 on macOs High Sierra (10.35.5). Getting this error message:

 

fatal: could not read Password for 'https://[accountName]@bitbucket.[domain.com]': Device not configured

Fatal: Could not fetch release/1.0.3 from origin.

 

Anyone any experience in resolving this issue? Version 2.7.3 seems to have the same problem. Pulling/pushing/... is working correctly.

 

Thanks in advance,

Koen

19 answers

10 votes
iMark21 October 4, 2019
Ashutosh Dave October 5, 2019

This worked for me!! Thanks!

ray November 28, 2019

It worked! thank you 

Bruce Rudolph January 8, 2020

This fixed the problem on my Mac.

Wanja Krah May 12, 2020

Didn't work for me.

Claudio Wagner May 15, 2020

It worked! This fixed the problem in my Mac too.

Narendar Singh Saini July 27, 2020

Excellent, worked for me in less than a minute !!

Erfan Gholampour January 3, 2022

this solution saved the day! Thanks!

3 votes
koenverhulst July 12, 2019

Atlassian: please fix this. 
Version 3.2.1 (225) and still broken gitflow.

This has been an issue for over a year.

3 votes
ansis December 4, 2018

v. 3.0.1 (205) Device not configured with Git Flow when finishing feature or release. please fix. (MacOs 10.14.1)

Koen Verhulst December 4, 2018

+1

Atlassian .. please fix this.

Like jeanherman likes this
vincentheeten December 19, 2018

+1

Eric December 21, 2018

+1

rafaelagp December 21, 2018

+1

Nat Wales March 5, 2019

+1

Roody Dennis April 23, 2019

+1

2 votes
nagendra-taglr July 30, 2019

Atlassian developers are high on weed i guess from over a year. It is not at all acceptable from such big platform. 

They don't even reply on the queries and concerns. Highly disappointed. *Red flag* for this tool.  

1 vote
koenverhulst June 26, 2019

Atlassian: please fix this. 
Version 3.2.1 (225) and still broken gitflow.

This has been an issue for over a year.

nbabdul September 18, 2019

still facing 19th sep 2019

1 vote
Jorik June 21, 2019

Atlassian: please fix this. 
Version 3.2 (224) and still broken gitflow

1 vote
Eric December 21, 2018

Problem only happens when the release / feature / hotfix branch is tracked / pushed on origin. Local branched with gitflow do work 

1 vote
Virl August 22, 2018

Issue is still present in 2.7.6 (177) — git flow is broken because of it.

 

What the hell Atlassian??

0 votes
ray November 28, 2019

Still broken in 4.0(232) !!

0 votes
Sumsam Khan September 4, 2019

Still broken in 3.2.1

0 votes
koenverhulst June 5, 2019

Atlassian: please fix this ... 

0 votes
HPPI_Mike June 5, 2019

This is still broken in 3.2

0 votes
Koen Verhulst November 26, 2018

This does not seems to be solved in Sourcetree 3.0.1.

0 votes
Paul Bonneville September 13, 2018

I'm using OAuth with SSH and it is NOT working for me. Still getting:

fatal: could not read Password for 'https://XXXXXXXXX@bitbucket.org': Device not configured

Fatal: Could not fetch feature/1.15-ticket-work from origin.

0 votes
Jim Thomas August 24, 2018

Switching my account to use SSH instead of HTTP auth fixed the issue for me.

luckyclan September 4, 2018

I confirm this workaround is working!

Wanja Krah May 12, 2020

Didn't work for me

0 votes
bhuvidya August 22, 2018

Even though I found this annoying initially, once I worked out that git-flow is actually just a bash script, and that I could find it in the SourceTree app area (on my mac:  /Applications/SourceTree.app/Contents/Resources/git_local/gitflow/git-flow) - then I have just started using the command line on my repos a lot more. I still love the way a GUI like SourceTree shows me quickly exactly what changes have been made (as opposed to just the files). And if course being able to see a visual representation of the commit trees is great too, but overall I'm glad to be getting a lot better at using git in the terminal.

0 votes
Koen Verhulst June 25, 2018

Updated this thread: https://community.atlassian.com/t5/Sourcetree-questions/Device-not-configured-error/qaq-p/767223#U828835

I'm still unable to finish a feature with SourceTree.

Yves Vogl June 28, 2018

It's the same here and I'm pretty sure its related to Sourcetree (2.7.6 177) itself. From command line everythings works as expected. Even doing the steps of "Finish release" manually works.

Gideon King July 25, 2018

I'm having the same problem in 2.7.6 177 too.

0 votes
Petru Magdeleine June 25, 2018

Hi, 

Since the last release, we experience the same problem when trying to finish a feature (using Git Flow > Finish Current):

fatal: could not read Username for 'https://gitlab.com': Device not configured

Fatal: Could not fetch feature/xxx from origin.

 

Sourcetree 2.7.6 / macOs High Sierra

0 votes
Ana Retamal
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 14, 2018

Hi Koen! To which service are you connecting? Have you connected your account already following the steps at Connect your account?

For troubleshooting purposes, have you performed the same operation from the command line? What is the result?

 

Cheers!

Ana

Koen Verhulst June 15, 2018

Thanks for your reply Ana.

We are connecting to an on premise bitbucket server. Will try to perform the same operation from command line and post the result here.

Thanks,

Koen

Koen Verhulst June 17, 2018

Hi Ana,

I was able to finish the release using command line. However, I would expect it to work from Sourcetree.

Cheers,

Koen

Damian Rosair July 17, 2018

Hi Koen,

I have had the exact same issue as you. Trying to finish a release on macOS High Sierra after updating to 2.7.6 SourceTree and no luck.

I've spent so much time updating the BitBucket server and resetting passwords but no luck.

This has happened before too so I should have remembered.

The command line worked for me too, and now I can use SourceTree again.

Thanks!

Damian Rosair July 18, 2018

Just a follow-up. SourceTree worked after reverting back to 2.6.3 with no issues at all.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events