Hi Mansour, this issue was reported in our bug tracker at SRCTREEWIN-7244. Our developers rolled 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.
Let us know if you need any further assistance!
A vulnerability has been published today in regards to Sourcetree for Windows. The goal of this article is to give you a summary of information we have gathered from Atlassian Community as a st...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event