Hi Yashu, this issue was reported in our bug tracker at SRCTREEWIN-7244. It was fixed already, but if you haven't upgraded 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!
Have you set them to the right location? Make sure that the accounts.json file is located at:
Follow the steps as below:
If this doesn't work, you'll need to check the following:
If after these steps you're still having trouble, let us know which Sourcetree and OS version are you using, your Internet Explorer version, and if you're in any kind of unusual environment (corporate , behind a proxy, etc)
Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...
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