Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

SourceTree remote repository settings not saving again

Hi.  Something similar happened in a previous version where changing remote settings wouldn't save, but it was eventually fixed.  Now in the most recent update, what it won't save is Optional Extended Integration Remote Account.  It keeps defaulting back to Generic Account once a day instead of keeping jraymond-gr Bitbucket selected.  I guess I could just roll back to the previous version if I can find an installer, but maybe this will just draw Atlassian's attention to the problem?  Or maybe someone has a fix?  Thanks!

- joe -

17 answers

1 accepted

4 votes
Answer accepted

Finally, version 4.3.4 fixes this issue, at least for GitLab remote accounts, maybe all the others too.

Upgraded from 3.2.6 to 3.4.3, which fixes it for BitBucket accounts too.

  • Fixed Optional integration settings not being saved
Like # people like this

Oh, that sounds great.  I'm going to stay at the old working version, but if people agree it works, I'm happy to mark this as the answer.  Thanks!

Alexander I believe i mean version 3.4.3, right? Anyways, version 3.4.3 fixed this issue for me. Finally!

This is happening to me too

If this is happening to you, make sure you go to the bug report for it and comment/like/watch:

Hmm, looks like there are 7 or 8 bugs on this, all marked as "Needs Triage", even ones that are 4 months old. Are they really just ignoring all bug reports?

Yes, they ignore them. Even for the paid products.

Their "New improved navigation", that actually is the same as it was years ago, is obviously so much more important.

+1 same here on windows 10 and v

Happening to me too, i am on version 3.3.8, the current last version

Same here.  Version 3.3.8 on Windows 10.  It forgets after the app is restarted.  As long as the app keeps running, it remembers; even if you close a repo tab and then re-open it.

Like # people like this

BTW, my specific situation is GitHub Enterprise integration.  I tried uninstalling and wiping the %APPDATA% & %LOCALAPPDATA% folders as described in Nasel's solution below.  I then installed v3.3.9.  Problem still happens.

One thing I noticed is that the .git\sourcetreeconfig.json file contains the extended info after I save it in SourceTree, and remains there after restarting it.  But then, as soon as I open a tab for that repo, the .git\sourcetreeconfig.json file gets updated and the extended info is now gone.

Yes, it seems like any exception that happens when opening a repo wipes the settings. Can you find your log file? Does it say anything? There have been enough clues in there for several of us to get to the bottom of our particular issues.

You can go to the related bug list and add a statement to the most appropriate one, but it doesn't seem like Git is high enough on the priority list at Atlassian for anyone to even triage their bugs.

You mean %localappdata%\Atlassian\SourceTree\sourcetree.log?  No exceptions.  A lot of messages like this:

ERROR [2020-08-15 19:39:46,536] [1] [SourceTree.Model.Repository] [Log] - Repository: [] does not exist

I'm not sure if it's the right solution, but I've found a way to solve this phenomenon and will share it.
I've been suffering from this phenomenon since the upgrade to Soucetree 3.3.4, and even after upgrading to 3.3.8, I haven't been able to solve it and am in trouble.
However, by re-installing Sourceetree and re-registering the bookmark of the repository in the next step, this phenomenon was released.
However, the reinstalled version is 3.3.6 for Windows.

■ Procedure (Windows 10)
1. Uninstall Source Tree from Apps and Features
For Windows 7, it is "Programs and Features" in the Control Panel.

2. Delete the "Atlassian" and "Soucetree" folders from the following folders (when the OS drive letter is C)
・C: / users / <user name> / AppData / Local
・C: / users / <user name> / AppData / Roaming

3. Install any version of Sourceetree

■Notes on work
-The folder location accessed in step 2 is for Windows 10. It may be different on other Windows.
-The folder accessed in step 2 is a hidden folder.
-The folder accessed in step 2 is a very delicate area used by the system and applications. Modifying other than the desired folder may adversely affect the system. Please work carefully.
-If you are using the built-in Git, the version of the built-in Git will be replaced with that of the Sourcetree installer you are installing. If necessary, please update the built-in Git from the "Git" tab in "Options" of the "Tools" menu.

I hope this information helps you.
Thank you.

*I am translating it into English with Google Translate. I am afraid there is something wrong with the text, but please forgive me.

Actually I think it worked. Thanks Nassel! 
I removed v 3.3.8, downloaded 3.3.6 and it seems to work now.

Tomorrow (19 June 2020) I will confirm!


UPDATE (18 June 2020)

 v 3.3.6 seems to have another bug. It doesnt refresh the UI after commit, push, merge...

You always have to press F5. I'll try a reboot and see what happens. Restarting the app didn't solve.

Reboot didn't solve, so I downgraded to 3.3.4.
Now it does refresh, but it "forgets" the remote accounts. Incredible. I'll try an older version.
I'm speechless.


UPDATE (19 June 2020)

Yesterday after downgrading to 3.3.4 I was notified about the 3.3.9 update, so I ran the update.

So nothing, even 3.3.9 forgets remotes. I'll keep this for now, but at this point I'll consider moving to Fork.


FINAL UPDATE (19 June 2020)

I solved all of my issues by uninstalling everything, deleting the folders under %APPDATA% as Nassel suggested and installing v 3.2.6 enterprise.

I'll stick with this for a while ;)


Antonino, thanks for the reply.

The UI not updating issue is a serious bug in Sourceetree 3.3.6.
Information about this issue is in a separate thread.

However, this phenomenon does not occur on the current PC.
Is it due to a clean installation? but this is a guess.

Antonino, I read your reply and thought:
1. Summarize the situation that occurred
-Updating from version 3.3.4 or earlier to version 3.3.6 or later results in a bug where remote accounts are not remembered.
-This issue does not occur with a clean installation of 3.3.6.
-It occurs when uninstalling 3.3.6 and installing 3.3.4.
2. Predict the cause
-It occurs when the update function of Sourcetree is used.
-It occurs when you uninstall and then install another version.
→ Is it caused by "Run the installation with the source tree file in /appdata/"?

Two tests are based on this guess.
-Update from problem-free 3.3.6 to latest version
-Clean install the latest version using the method I suggested.

Once the test is complete, report each result.


UPDATE 24 Jun. 2020

I was making a mistake. sorry.
A critical bug in 3.3.6, the UI not updating, was actually happening. It seems that I pressed the F5 key to update the display.

■Here is the report of verification results.
We are also conducting verifications other than the above, so we will report it together.

・Updated from 3.3.6 to 3.3.9
Result: Symptoms occurred
I could not use the update function, so I updated it with the installer.
When I started it, the remote button wasn't working anymore.

・Uninstall 3.3.6 and install 3.3.4 as is.
Result: Symptoms occurred
We were able to confirm the reproducibility of the phenomenon that occurred on the Antonino's PC.

・Clean installation of 3.3.4, 3.3.8, 3.3.9
Result: Symptoms occurred
You can use the remote button immediately after installation or immediately after adding a bookmark.
However, when I close SourceTree, the buttons stop working again.

· Clean install 3.3.6 again
Result: Symptoms may occur
I didn't understand. Why do the symptoms come back?
I installed 3.3.6 cleanly 3 to 4 times, but the phenomenon continued to recur.
The next day, I tried a clean installation 3.3.6 again, but the symptom did not occur. Repeating the clean installation 5-6 times a day did not cause any symptoms.

・Clean installation 3.2.6
Result: Works fine

■ What is discovered and what can be inferred from the results
・This issue has occurred since 3.3.4 and has not been improved in the latest version 3.3.9 on June 24, 2020.
・You may not be able to successfully perform a clean installation of 3.3.6.
・In 3.2.6, the phenomenon did not occur in the first place
・3.3.6 is not a solution to any other problem (reproduce bugs such as UI not being updated automatically)

I think the solution in the procedure I wrote works with SourceTree 3.3.6 or 3.2.6 or earlier.
Use 3.3.6 if you can tolerate issues with UI not updating automatically on F5, and use 3.2.6 if you want more stable behavior.

* Translated into English with Google Translate. I think there is a problem with the text, but please forgive me.

Like KrixS likes this

I'm glad I found this thread. I'm also having the issue. Not sure exactly which tracking ticket to note it on, so I just updated the one higher up in this thread. (

I went to the download archives and got 3.3.6 for Windows. It doesn't seem to have the Optional Extended Integration credential saving problem. (Download archive:

Hope that helps someone else. I beat my head against this for a day before thinking to do this search. >_<

Thanks!  Yeah, that DOES fix it.  Nice find.

Weird, I was having this problem on 3.3.6, and upgraded to 3.3.8 in hope it would solve the issue.

:(  I'm usually the one that fixes don't work for.  It feels nice to have something work in my favor for once.

I am also on 3.3.6 and have the issue. I upgraded to 3.3.8 and still had it, and downgraded to 3.3.4 and still had it.

YES this finally worked for me. Downgrading from just installed version 3.3.9 which did not fix the issue, to 3.3.6 now did fix it. I think i will stay with this for now :)

Same problem and it effects other issues such as subtree dissappearing.

Seems like sourcetreeconfig.json file is not saved properly when closing the program. 

same problem 3.3.9

And still in December 2020…

Like Rodrigo Hernangómez likes this

I'm experiencing the same issue.
Saved remote account, then closed/opened app and it doesn't save anything.
fyi: my version is v.3.3.9
please help us.
thank you

same problem

I found a fix that works on 3.3.6, and will probably also work on 3.3.8.

While poking around I found the log file, and saw an exception failing to load a TimeZoneConverter library that it couldn't find. I went to and downloaded the package. It is just a zip file so I extracted timezoneconverter.2.3.0.nupkg\lib\netstandard2.0\TimeZoneConverter.dll and put it into %AppData%\Local\Atlassian\SourceTree\hg_extras, and now it doesn't reset to Generic Account any more! Yay!

Just tried this on 3.3.8 and isn't working for me unfortunately.

Still happeing to me at least last two version... buggy software... march 2020

Same problem for me, and for a while now...

Same thing happens to me. may 2020 and still not fixed

November 2020. still not fixed.

Like Rodrigo Hernangómez likes this

March 2021. Finally fixed on version 3.4.3. thanks guys

Happening to me also. There are some workarounds but all seem to be temporary. I think Atlassian may be aware of the issue as it's been widely reported but have not taken any action to resolve it yet.

v3.3.9, an issue exists, I need to update remote settings after each program load.

This issue also effects the subtree settings... I went back 3.2.6. and the problem is gone.

It was working in 3.3.6, and it still does not work in 3.3.9. I remember that it was also not working in another version after 3.3.6.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events