Sourcetree crashes when I try to add a remote account

[swlgroup]

Last Friday I updated to Sourcetree 3.3.9 (Windows 10) (from version 2.something) and tried to add a remote account on the add repositories screen. Every time it spins for about 2 seconds then crashes. If I go to 'clone' and click the "cloning is easier if you setup a remote account" link it does the same thing.

Each time it generate a sourcetree log with the same content:

2020-12-21T08:57:04: LogHost: Initializing to normal mode
2020-12-21T08:57:06: ReactiveList`1: Property change notifications are enabled and type SourceTree.Model.RepositoryRemoteProjectLink isn't INotifyPropertyChanged or IReactiveObject
2020-12-21T08:57:06: ReactiveList`1: Property change notifications are enabled and type SourceTree.Model.RepositoryRemoteProjectLink isn't INotifyPropertyChanged or IReactiveObject
2020-12-21T08:57:06: Could not obtain git dir, C:\Users\[xxx]\AppData\Local\SourceTree\app-3.3.9 is not a git repo.
2020-12-21T08:57:06: Could not obtain git dir, C:\Users\[xxx]\AppData\Local\SourceTree is not a git repo.
2020-12-21T08:57:06: Could not obtain git dir, C:\Users\[xxx]\AppData\Local is not a git repo.
2020-12-21T08:57:06: Could not obtain git dir, C:\Users\[xxx]\AppData is not a git repo.
2020-12-21T08:57:06: Could not obtain git dir, C:\Users\[xxx] is not a git repo.
2020-12-21T08:57:06: Could not obtain git dir, C:\Users is not a git repo.
2020-12-21T08:57:06: Could not obtain git dir, C:\ is not a git repo.
2020-12-21T08:57:11: LogHost: SuppressChangeNotifications was called (perhaps via AddRange), yet you do not
2020-12-21T08:57:11: LogHost: have a subscription to ShouldReset. This probably isn't what you want, as ItemsAdded
2020-12-21T08:57:11: LogHost: and friends will appear to 'miss' items
2020-12-21T08:57:13: VaultClient::ReadCredentials

A second sourcetree.log file repeats the following each time the system crashes

ERROR [2020-12-21 09:32:51,136] [49] [SourceTree.Exceptions.RemoteHostException] [Log] - Insufficient authentication credentials
ERROR [2020-12-21 09:32:51,149] [1] [SourceTree.Exceptions.RemoteHostException] [Log] - Failed to list teams for user [etuna]
ERROR [2020-12-21 09:33:03,727] [1] [SourceTree.Model.Repository] [Log] - Repository: [] does not exist
ERROR [2020-12-21 09:33:03,786] [1] [SourceTree.Model.Repository] [Log] - Repository: [] does not exist
ERROR [2020-12-21 09:33:03,801] [1] [SourceTree.Model.Repository] [Log] - Repository: [] does not exist
ERROR [2020-12-21 09:33:03,815] [1] [SourceTree.Model.Repository] [Log] - Repository: [] does not exist
ERROR [2020-12-21 09:33:03,830] [1] [SourceTree.Model.Repository] [Log] - Repository: [] does not exist
ERROR [2020-12-21 09:33:03,845] [1] [SourceTree.Model.Repository] [Log] - Repository: [] does not exist
ERROR [2020-12-21 09:33:03,870] [1] [SourceTree.Model.Repository] [Log] - Repository: [] does not exist
ERROR [2020-12-21 09:33:03,885] [1] [SourceTree.Model.Repository] [Log] - Repository: [] does not exist
ERROR [2020-12-21 09:33:03,900] [1] [SourceTree.Model.Repository] [Log] - Repository: [] does not exist
ERROR [2020-12-21 09:33:03,914] [1] [SourceTree.Model.Repository] [Log] - Repository: [] does not exist
ERROR [2020-12-21 09:33:03,929] [1] [SourceTree.Model.Repository] [Log] - Repository: [] does not exist
ERROR [2020-12-21 09:33:03,943] [1] [SourceTree.Model.Repository] [Log] - Repository: [] does not exist

Any ideas?

[Soumyadeep Mandal]

Hi @swlgroup ,

Welcome to the community! We are glad you are here!

Wish you a very happy new year!

Can you please try a clean install? The steps are as follows:

1. Wipe SourceTree preferences. 
2. Uninstall SourceTree (if it shows on the App&Features list)
3. Backup then delete the directory below before proceeding with the next step
• Navigate to C:\Users\<UserName>\AppData\Local and delete SourceTree & SourceTree-Settings folder
• Navigate to C:\Users\<UserName>\AppData\Local\Atlassian and delete all SourceTree Files/Folder.
4. Download SourceTree and install it. 

Regards,

Soumyadeep (SaM)

[jhpeterson]

I have this problem too. The suggested action is too severe. there is too much setup, config, etc stuff to reenter to get it running again. surely there must be a non-nuclear option.