Hi! This issue was reported in our bug tracker at SRCTREEWIN-7244. Our developers are rolling a fix, but if you haven't been prompted for the upgrade yet you can use the following workaround:
From a working install collect the accounts.json and passwd files.
Delete the Atlassian folder from the AppData/Local directory for your user. Run the installer for 2.3.1, close it when you get the blank login window. Place the account.json and passwd files into the Atlassian/SourceTree folder. Rerun the installer. It should detect the account and password from those files and bypass the request for a login.
Please make sure the email address used in the file is valid, yours and associated with a valid Atlassian account, in order to be in compliance with the Atlassian EULA.
In the future, it's a good practice to do a search within the Atlassian Community first as someone else might have already asked the same questions as you and you might be able to find the solution quicker. This question for example has been asked in the Community repeatedly :)
Let us know if you have any questions!
Hi, if you read through the comments in the bug ticket you'll find the solutions proposed by the users. In this comment a user posted an example file that you can use.
You can also go through the rest of the comments to see what other users did.
Hope that helps!
Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs