When I launch sourcetree it quits unexpectedly, we've tried downgrading to a previous version, removed preferences, removed folder from application support, restarted machine etc etc
We are running 10.12.6 Sierra
However, after a bit of digging around, we've found a file in the .git folder called:
sourcetreeconfig
If I delete this file and restart source tree, it works and another sourcetreeconfig file is created.
Example of sourcetreeconfig before deleted:
remoteProjectLink0.remoteName=origin
showBuildStatus=1
remoteProjectLink0.type=0
remoteProjectLink0.username=USERNAME
savedIncoming=0
disablerecursiveoperations=0
remoteProjectLink0.identifier=USERNAME/PROJECTNAME
remoteProjectLink0.baseUrl=https://www.bitbucket.org
autorefresh=1
savedOutgoing=0
lastUsedView=1
autorefreshremotes=1
lastCheckedRemotes=2018-06-06 09:58:31 +0000
Example of sourcetreeconfig after being recreated on app launch:
autorefresh=1
savedIncoming=0
lastUsedView=1
savedOutgoing=0
lastCheckedRemotes=2018-06-06 09:57:24 +0000
disablerecursiveoperations=0
showBuildStatus=1
autorefreshremotes=1
I know I could delete this file everytime I want to download one of the projects, but is there a solution to this?
UPDATE
This doesn't work now, even though we've deleted, it's not recreating the config file.
Thanks
Dan
We are investigating the crash with https://jira.atlassian.com/browse/SRCTREE-5762. There seems to be an issue loading and reading repo avatars. We will soon have an update on this. In the meanwhile, feel free to remove the ImageCache folder under ~/Library/Application Support/SourceTree/
Thanks for your patience!
Manjunath
Sourcetree Mac Developer
Solution here to downgrade to 2.3.2 fixed it for me : https://jira.atlassian.com/projects/SRCTREE/issues/SRCTREE-5770?filter=allopenissues
Bigger thread with same issue: https://community.atlassian.com/t5/Sourcetree-questions/Sourcetree-crashes-on-startup-on-MAC/qaq-p/813621#U813696
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.