Hi Nitiz, 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.
Note that in order to be in compliance with the Atlassian EULA you must ensure the email address used in the file is valid, yours and associated with a valid Atlassian account.
For the future keep in mind that if you do a search within the Atlassian Community first you might be able to find the solution to your problem much faster, as it might have already been asked. This question for example has been asked in the Community repeatedly :)
Let us know if you need any further assistance!
Cheers,
Ana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.