I recently tried upgrading SourceTree 126.96.36.199509 to 188.8.131.52 on a Windows Server 2012 VM.
It seemed to go fine, until I got to signing in with my existing Atlassian account. After entering my credentials, the upgrade program displayed some kind of HTTP error 403 and would not continue. My default browser is Chrome (the latest version) on that box.
I was able to uninstall 184.108.40.206, then reinstall 220.127.116.11509 to recover my settings with very little pain. But I am not anxious to try another 1.8x upgrade, as I do not want to risk having to set up all my repos again.
I was able to upgrade with no problems on my Windows 8.1 box (using my same Atlassian account credentials).
Anyone else see anything like this?
Anyone else upgrade on Windows Server 2012?
To close the loop on this:
After I upgraded then launched the new SourceTree, I was forced to sign in with my existing Atlassian account (that requirement began with SourceTree v 1.8.2).
For that to succeed in my environment, however, I had to relax our ESC (Enhanced Security Configuration) and allow the Atlassian URL in question (id.atlassian.com IIRC). Then, after signing out and signing back in to Windows, the Atlassian sign in succeeded and I was able to use the newest version of SourceTree.
Supported Platforms macOS Sourcetree has a lot to offer and, like many developer tools, finding and using it all can be a challenge, especially for a new user. Everyone might not love ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot