Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

macOS Catalina - Terminal Button Always Opens in Home Folder

Steve King November 27, 2019

I just setup a new computer with macOS Catalina Version 10.15.1

I am running Sourcetree Version 4.0(232)

When I click the Terminal button on the top right, it always opens the terminal in my home folder and NOT the repository working directory.

I thought it was just a bug with the newer version of SourceTree, but I upgraded my old computer to Catalina and the same version of SourceTree, and my old computer opens the terminal in the correct repository directory.  I notice that somehow a cd command takes place immediately after the terminal is launched, but my new computer won't do that.

I have compared settings between the two computers, searched everywhere I can find, and I cannot figure out how to get Sourcetree to change directory in the terminal on my new computer.

It's pretty inconvenient to have to cd manually every time I open a terminal window.  Help!

 

Thanks,

Steve

11 answers

1 accepted

19 votes
Answer accepted
Mike Dammers January 2, 2020

This worked for me:

  1. Uninstall current version.
  2. Install old version (3.2.1) from https://www.sourcetreeapp.com/download-archives
  3. Press the terminal button and it will ask for folder permissions.
  4. After giving the permission, uninstall the old version and install the the latest version again.
Steve King January 2, 2020

Thank you, Mike.

Like douglaskazumi likes this
Olivier Guilleux February 20, 2020

Thanks a lot !

fernando March 10, 2020

Obrigado!

Like Steve King likes this
nfantozz March 11, 2020

Thanks a lot. This worked for me. Only took about 2 minutes.

  1. Downloaded version 3.2.1
  2. Extracted and moved the sourcetree.app file to the applications folder and replaced the current one.
  3. Opened SourceTree
  4. Clicked the terminal icon, it will prompt for permissions. Allow it. ;)
  5. Checked for, and updated to 4.0
  6. Relaunched.
Like # people like this
Bestiosfreelancer2 March 11, 2020

Thanks!

segur March 13, 2020

Thanks a lot. But it's not worked for me. :(
I downgraded to version 3.2.1 and clicked the terminal icon, but it did not prompt for permissions.

Steve King March 31, 2020

Now install the newer version. It should work after that. 

dmitry1100 April 8, 2020

Thank you, Mike! Your solution with temporary downgrade really works!

Like Steve King likes this
segur April 8, 2020

The following steps worked on my Mac.

  1. Uninstalled SourceTree 3.2.1
  2. Installed SourceTree 2.7.1
  3. Installed iTerm2 Build 3.3.9 (the latest version in Homebrew)
  4. Clicked the terminal icon, then the permission dialog was displayed.
  5. Upgraded to SourceTree 4.0.1

Thanks.

segur April 8, 2020

The following steps worked on my Mac.

  1. Uninstalled SourceTree 3.2.1
  2. Installed SourceTree 2.7.1 (159)
  3. Installed iTerm2 Build 3.3.9 (the latest version in Homebrew)
  4. Clicked on the terminal icon, then the permission dialog was displayed.
  5. After giving the permission, upgraded to SourceTree 4.0.1 (234).

Thanks.

farhan.khan June 17, 2020

It worked, thanks!

PhiFry June 22, 2020

You don't need to uninstall and reinstall the latest version, just download and extract and run the 3.2.1 version in the downloaded folder and click Terminal and accept permissions, then just delete the 3.2.1 version and continue with the latest as usual.

Like Steve King likes this
Drenov November 13, 2020

I was looking for that for a year! Thanks!!

Emily Fung November 13, 2020

Do we know why this bug exists and why Atlassian still not be able to fix it?

1 vote
yuki.mishima April 3, 2020
  1. Open macOS's System Preference
  2. Security & Privacy
  3. Privacy tab
  4. Automation in the left pane
  5. Check SourceTree.app's Terminal

Steve King April 4, 2020

I had already solved this a while back, but this looks like it might have worked!

PhiFry June 22, 2020

Sourcetree isnt present there unless youve already accepted permissions in pre 4.0 version. Follow accepted answer instead.

Like Steve King likes this
1 vote
Emily Fung March 30, 2020

I agree with  Nguyen, is there an actual fix yet from Atlassian?

1 vote
Ihar_Tsimafeichyk December 23, 2019

Same issue for me, to make it work I had installed sourcetree older version

Steve King December 23, 2019

I'll have to try that.  Thank you!

0 votes
Mikael Nensén March 7, 2021

I can't believe this still hasn't been fixed, I've been living with this for ages and just now found the fix because I decided to fix it. 

0 votes
Rahul Agrawal July 31, 2020

Worked for me - had the same trouble after I updated to catalina last night

Installed older version 3.x

Ran the open terminal from sourcetree

gave the permission

close source tree

downloaded the latest version

installed it

Mac blocked the latest version as un trusted.

Gave the permission via security and privacy setting

worked fine

Thanks to all those who contributed here to help.

0 votes
Hieu January 12, 2020

Same issue. I don't want to reinstall the older version.

Steve King January 13, 2020

It's just a temporary measure.  As soon as you install the older version, upgrade to the latest.

Like llinardos likes this
PhiFry June 22, 2020

You dont have to uninstall and reinstall/upgrade to latest again, just download and extract 3.2.1 and run it in whatever folder you downloaded it to and click terminal button and delete the 3.2.1 version and continue using the latest.

Like Steve King likes this
0 votes
Mike Penz December 19, 2019

Same issue here

0 votes
Steve King December 17, 2019

Well it's nice to know I'm not alone, but anybody have any ideas?  Is there a way to get support?  Does someone knowledgable at Atlassian ever check these boards?

0 votes
Terko December 15, 2019

Same thing happens to me on Catalina and my new computer. Doesn't happen on old computer on Catalina. 

0 votes
daniel.benito December 3, 2019

Same thing happens to me (same macOS ad SourceTree versions), also, open in terminal is no longer opening a new terminal window when the Terminal is already open.

Steve King December 3, 2019

Same here with not opening a new window when Terminal already open.

Any answer?  A solution anybody??

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events