nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Checkout in sourcetree not working after upgrade to v2.x

Dan Neely_fwpz9a

After upgrading my client from 1.x to 2.x the Checkout in Sourcetree links in bitbucket don't work.

In Firefox I was able to change the path to sourcetree for the handler to its new location `C:\Users\dneely\AppData\Local\SourceTree\app-2.0.20.1\SourceTree.exe` but other than a wait cursor spinning for a second in the browser nothing happens. (And even if it did work now, won't baking the executable version number into the path mean that I'll need to fix it every time it updates).

Chrome doesn't even do that much, and I can't find a way to change the app association. The only documented solution I could find on how to do so appears to be out of date (or Google is doing something different on Windows) because my `Local State` file doesn't have any text matching `protocol_handler` or any varients of sourcetree that I tried.

Digging into my registry based on one answer I found the following key:

> HKEY_USERS\S-1-5-21-310591559-4105708594-108812639-1110\Software\Classes\sourcetree\shell\open\command

with the value:

> "C:\Users\dneely\AppData\Local\SourceTree\app-2.0.20.1\SourceTree.exe" -url "%1"

The latter is the location that sourcetree installed itself on my computer. Tools-Options-General-Use this version of SourceTree for URI association is checked.

Hermo Terblanche that a sourcetree process was starting and dieing after a few seconds I went hunting for and found the `\AppData\Local\Atlassian\SourceTree\sourecetree.log` file. Each instance of ST that is spawning and crashing a few seconds later is writing an instance of this into the file.

ERROR [2017-06-12 10:16:29,006] [1] [SourceTree.App] [OnStartup] - Failed to start
System.NullReferenceException: Object reference not set to an instance of an object.
   at SourceTree.Host.Bitbucket.BitbucketHost.GetCanonicalUri(IConfigurationManager configurationManager)
   at SourceTree.Host.Bitbucket.BitbucketHost.get_CanonicalUrl()
   at SourceTree.AppRoot.HandleExtendedIntegrationUrl(Boolean isFirstInstance, String url)
   at SourceTree.AppRoot.ProcessArguments(Boolean isFirstInstance)
   at SourceTree.AppRoot.DoWindowStartupTasks()
   at SourceTree.ViewModel.MainWindowViewModel..ctor(IRepositoryTabContainerViewModel repositoryTabContainerViewModel, ICustomActionsManager customActionsManager, IRepositoryManager repositoryManager, IAnalyticsDataManager analyticsDataManager, ITraceManager traceManager, IDispatcher dispatcher, IAccountManager accountManager, IFailureHandler failureHandler, IDvcsManager dvcsManager, IConfigurationManager configurationManager, IInstanceManager instanceManager, ISchedulerManager schedulerManager, IWebManager webManager, IRepositoryMonitorManager repositoryMonitorManager, ISshKeyManager sshKeyManager, INotificationsManager notificationsManager, IPreferencesManager preferencesManager)
   at SourceTree.MainWindow..ctor(IRepositoryTabContainerViewModel repositoryTabContainerViewModel, ICustomActionsManager customActionsManager, IRepositoryManager repositoryManager, IAnalyticsDataManager analyticsDataManager, ITraceManager traceManager, IDispatcher dispatcher, IAccountManager accountManager, IFailureHandler failureHandler, IDvcsManager dvcsManager, IConfigurationManager configurationManager, IInstanceManager instanceManager, ISchedulerManager schedulerManager, IWebManager webManager, IRepositoryMonitorManager repositoryMonitorManager, IApplicationManager applicationManager, ISshKeyManager sshKeyManager, INotificationsManager notificationsManager, IBookmarkManager bookmarkManager, IPreferencesManager preferencesManager)
   at SourceTree.AppRoot.OnStartup(StartupEventArgs e)
   at SourceTree.App.OnStartup(StartupEventArgs e)

Still not working in 2.1.2.5

Just tried uninstalling, nuking all sourcetree related data I could find from my system and reinstalling. This included:

1. All Sourcetree registry keys.

2. C:\Users\<username>\AppData\Local\Atlassian\*

3. C:\Users\dneely\AppData\Local\SourceTree\*

4. C:\Users\dneely\AppData\Local\SourceTree-Settings\*

5. C:\Programdata\Atalassian\*

After doing all of this and reinstalling I still get a second sourcetree prosess spawning for several seconds and then dieing without launching the checkout in sourcetree dialog.

2017/08/11 update. Still broken in 2.1.10.0

Accepted answers

All comments

bquirk

also experiencing this issue after upgrading to 2.x this morning. In the meantime you can fetch from origin and check the branch out that way until it gets fixed.

unknown

Hi Dan,

Try toggling the setting called: Use this version of SourceTree for URI association

Tools > Options >General

There is a setting "Use this version of SourceTree for URI association" this should be checked.

If it is but the clone from Bitbucket is still not triggering SourceTree, can you try toggling that option off then on again. This should force a re-write of the registry setting needed by Windows.

I stole this answer from Michale Minns.

https://jira.atlassian.com/browse/SRCTREEWIN-6350

Dan Neely_fwpz9a

I just tried that; it was initially checked and unchecking and rechecking it didn't work. I also tried restarting sourcetree after clearing the checkbox and then settting it again in case the setting wasn't immediately written to the registry. The uncheck/recheck states came through, but after being rechecked it still didn't work.

bquirk

Thanks this worked for me. I had to uncheck it, save the dialog, then re-open and re-check the setting before it would work.

unknown

Didn't work for me either

unknown

I am also experiencing the issue. It seem to only work if SourceTree is already running before you click "Checkout in Sourcetree" from the browser.

If SourceTree is not running before clicking "Checkout in SourceTree", nothing happens. I can momentarily see the SourceTree process starting, but it soon disappears thereafter.

This used to work in v 1.x

I have tried all the workarounds, but believe the issue is not with the registry setting, but the actual exe.

Dan Neely_fwpz9a

It's not working for me either way. Task manager shows a second sourcetree process spin up if I have it already running, but like the second one in the case where it was already running, it goes away after a few seconds without doing anything.

It's been nearly a month, and I'm getting increasingly frustrated by Atlassian's lack of response. Especially since the security flaws in 1.x mean that I can't downgrade to a working version while they try to figure it out.

unknown

Great work with finding the logs. Lets hope this provides them enough info to fix this.

unknown

I created an interesting workable solution for this bug. It is capable to "Checkout in SourceTree" even when SourceTree is not already running.

The idea is based on a batch file that first launches SourceTree normally, and soon thereafter launches it again with the -url parameter.

Instead of having the original value in the sourcetree/shell/open/command registry key

"C:\Users\<yourname>\AppData\Local\SourceTree\app-2.0.20.1\SourceTree.exe" -url "%1"

you replace the above value with

"C:\Users\<yourname>\Documents\CheckoutInSourceTree.cmd" "%1"

The content of CheckoutInSourceTree.cmd looks like this:

setlocal
pushd "c:\Users\<yourname>\AppData\Local\SourceTree\app-2.0.20.1"
START sourcetree.exe
TIMEOUT /T 1
START sourcetree.exe -url %1

Let me know how this works for you!

unknown

setlocal resets your environment to whatever path was the current directory before running the batch

timeout is necessary to make sure that the first instance of sourcetree is started before calling it again with the -url parameter

Dan Neely_fwpz9a

This didn't work for me, but since my install is more broken than yours in that checkout in sourcetree doesn't work in both the running and not running cases I didn't expect it to. The only visible impact was that in task manager I now have two ephemeral copies of ST starting and then dying a few seconds later.

unknown

Sorry to hear. If you only tested with the batch file you could verify if it still does not work if you start SourceTree manually, wait till it shows the UI, and then see what Checkout in SourceTree does.

You can also increase the timeout in the batch between the two calls to sourcetree.exe. Maybe on slower machines this timeout need to be bigger. I've found that if I completely remove the timeout, it does not work for me either as it does not guarantee that the first call to sourcetree.exe happens before the second.

Dean Kinane

Hi Dan

Did you ever get this working again?

I have the same issue since upgrading to v2.

Currently on 2.1.2.5 and it's still l not fixed.

I've tried all the suggestions and nothing has worked for me.

Best regards,

Dean

Dan Neely_fwpz9a

nope, I'm still stuck too.

Dean Kinane

That's a shame.

Hopefully it'll be fixed in the next update.

Dan Neely_fwpz9a

Atlassian's well past the point where they've lost all my good will by refusing to publicly acknowlege that there's a lingering problem that can't be fixed by turning it off and back on. They've probably permanently written themselves out of consideration for anything where I get to choose the techstack (vs my employer doing so). As is, I'm only still using sourctree because I've been too busy to try out replacements.

If that afternoon of free time happens before they can be bothered to fix this - or more likely fix it by accident - I'll be gone never to return. Even then I still might leave. None of the 1.x performance fail cases they supposedly flxed ever affected me; and 2.x is constantly decorating itself with wait spinners for things that just worked before a foreverday security bug forced me to downgrade to the newer version of the product.

Didier Poulain

Still not fixed in 2.4.7.0

I'm on Windows 10.

The process launched is:

"C:\Users\XXXX\AppData\Local\SourceTree\app-2.4.7\SourceTree.exe" -url "sourcetree://checkoutRef/?ref=
refs/heads/XXXXXXXX&cloneUrl=git@bitbucket.org:xxxxx/xxxxxx.git&type=bitbucket"

SourceTree starts and then exists immediately. I tried all suggested solutions.

Dan Neely_fwpz9a

Where did you find 2.4.7? I'm not seeing anything newer than 2.3.5.

Didier Poulain

I got an auto update this morning.

Dan Neely_fwpz9a

Do they do staged rollouts? I'm not seeing an update when I use the in app check feature, and their website's offering me 2.3.5 on its download page.

I can get 2.4.7 by manually editing the download URL...

SowmyaHari

hey is there a fix ?

Mike Corsaro

Hello! This issue will be fixed in the 2.4.8 release which should be available in the next week or so.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket

windows