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; } } }

Unable to Create Pull Request - Default Browser Empty

NathanGlanzerONE

When I try to do a Pull Request I get "Unable to open your web browser to ", do you have a default web browser set?

I do have a default. I've uninstalled, reinstalled, deleted settings, done everything and it isn't helping. I can't do my job without this ability what is going on?

Accepted answers

alondono

I was having the same issue with version 3.3.4 of Sourcetree, and this is what worked for me to fix it.

In Sourcetree, click on the "Settings" button, located on the top-right of the screen
On the window that opens, in the "Remotes" tab, select your remote and click "Edit"
If all the information is correct in that window (it was in my case), simply click "OK"
Click "OK" again to to close the "Repository Settings" window

That fixed it for me. It seems to me that re-setting the URL of the repository to the same address is what does the trick. I hope it works for you as well.

All comments

alondono

I was having the same issue with version 3.3.4 of Sourcetree, and this is what worked for me to fix it.

In Sourcetree, click on the "Settings" button, located on the top-right of the screen
On the window that opens, in the "Remotes" tab, select your remote and click "Edit"
If all the information is correct in that window (it was in my case), simply click "OK"
Click "OK" again to to close the "Repository Settings" window

That fixed it for me. It seems to me that re-setting the URL of the repository to the same address is what does the trick. I hope it works for you as well.

NathanGlanzerONE

Why in God's name did that just work? THANK YOU

alondono

Sadly, and I just noticed this, if you restart Sourcetree then you have to do this again.

It doesn't hold between sessions. At least not in version 3.3.4.

Eric Anderson

I just upgraded to 3.3.4. I also encountered such a problem and also find that the fix provided by this odd workaround is only temporary and doesn't hold between sessions.

I can add that I tried changing the following:

When Editing

under Remote details

in Optional extended integration

the setting for Remote Account was "Generic Account" (with "Bitbucket" chosen for "Host Type" under "Legacy Account Settings").

Instead of relying on "Generic Account", I tried changing it to the more specific Remote Account setting of "Bitbucket". Whether that mattered at all or not, after quitting and restarting Sourcetree the Remote Account setting was back to "Generic Account".

It doesn't seem to be doing very well at remembering changes to settings.

Eric Anderson

Even though there is an "accepted" answer, that was a workaround that doesn't last. So a real fix is still needed.

(As an aside, I wonder if this issue would get more attention if it didn't have any accepted answer.)

In the meantime, this old comment about an earlier problem with pull requests and remotes admitted the following possible alternate work around (my emphasis added).

Overall, more people in my company seem to have the issue than not, so we have mostly switched to creating the Pull Request through the JIRA interface.

alondono

I've created a new issue in the Sourcetree for Windows' Jira site.

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

Eric Anderson

In the meantime, while we await a fixed version of Sourcetree, is there a way to reinstall the previous version of Sourcetree (and then avoid upgrading until this Sourcetree bug is fixed)?

p.s. In https://jira.atlassian.com/browse/SRCTREEWIN-12482 you mention that the bug doesn't happen in version 3.2.4 (the last version of 3.2.* ?). However, when I look at

https://www.sourcetreeapp.com/download-archives

it seems that the last version they have listed for Windows is 3.1.3. Is there a way to get the last Windows 3.2.* version?

p.p.s. NOTE: No one should use any Windows Sourcetree versions earlier than 3.1.3 because of this remote code execution vulnerability.

alondono

Here is the official list of previous installers. Note that the last reported version is 3.1.3

https://www.sourcetreeapp.com/download-archives

You can access other versions not in the list if you copy one of the URLs and manually change the number. For example, manually change the last reported one

https://product-downloads.atlassian.com/software/sourcetree/windows/ga/SourceTreeSetup-3.1.3.exe

to 3.2.4

https://product-downloads.atlassian.com/software/sourcetree/windows/ga/SourceTreeSetup-3.2.4.exe

p.s. In https://jira.atlassian.com/browse/SRCTREEWIN-12482 you mention that the bug doesn't happen in version 3.2.4

You are correct. What I was trying to say is that 3.2.4 is not the version where I encountered the error. I upgraded from version 3.1.3 to version 3.3.4, but when you are creating the Jira issue you select the affected version from a drop-down list and the latest one that could be selected was 3.2.4. The version 3.3.4 was not still in the list.

François Fustin

17th December and the problem still exist.

Is there any chance to have a fix to put under the Christmas tree ?

Eric Anderson

A formal issue SRCTREEWIN-12482 was created on Nov. 7, but has not been updated since that day. Sadly, it is marked "Low" priority.

I would encourage anyone affected by this to add themselves to both the "Affected customers:" and "Watchers:" for that issue.

In the meantime, since the problem exists in 3.3.4 and any Windows version earlier than 3.1.3 has a software security vulnerability that should be avoided, my best recommendation is to download, install, and use version 3.2.6 (or else version 3.1.3 which also works), and then avoid automatic updates until the problem is truly fixed.

Eric Anderson

It has now been over 6 months since issue SRCTREEWIN-12482 was created, but it appears that no action has been taken to actually correct the introduction of that bug starting in 3.3.4.

MixJenkinsCI has added this comment:

"I'm on 3.3.8 and the problem is extremely irritating - can we raise the priority please - every time I restart SourceTree it has reverted back to GenericAccount and I have to set it to my user account - hordes of queries on the net about it"

Given that this is functionality that used to be working, how hard can it be to restore the past normal functionality? This isn't a request for a new feature, or even a request for any improvement beyond the functionality that already existed prior to 3.3.4.

pirod

v3.3.8 still has this bug

alondono

Some good news, the Jira ticket related to this item has now been moved to "In Progress", with a comment saying:

We are working on fixing this and releasing a new version as soon as possible.
Thanks for the patience. Meanwhile, you can join the beta program for frequent releases
https://groups.google.com/g/atlassian-sourcetree-beta

alondono

This issue has finally been fixed in Sourcetree 3.4.3. It can be downloaded here:
https://product-downloads.atlassian.com/software/sourcetree/windows/ga/SourceTreeSetup-3.4.3.exe

grrinch

I installed the latest version and the bug is still there...

alondono

@grrinchcan you not create pull requests in Sourcetree 3.4.3?

If you cannot, first try the workaround that was suggested here in the accepted answer, then try creating a pull request. From then on, it should keep working correctly even after restarting Sourcetree.

grrinch

done that - these were the first things I did. Well, I'll wait for 3.4.4 then

Welcome!

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

Quick Links

Find more posts tagged with

sourcetree