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 not remembering Stash details (extended integration)

Sourcetree will not remember my settings for Stash under Optional Extended Integration for any of my repos.  I try to create a pull request and I get a message saying I have to configure the extended integeration.  I add my stash details and the pull request will work.  A day or two will go by, I probably quit and re-open sourcetree several times, then try another pull request. I get the same message saying I don't have any extended integration configured. I keep having to re-enter the details.

12 answers

3 votes
Ana Retamal Atlassian Team Aug 02, 2017

Hi Mark, are you using SourceTree for Windows or for Mac? And which version? We do have a bug regarding the issue you described but it was fixed already, you can find it at SRCTREEWIN-6954.

If you're in the newest SourceTree version (which can be found at and are still experiencing this problem, please let us know so we can look into it!

Best regards,


I am using SourceTree for Windows version

Any update? I am still having this issue (just happend again now) using the current windows version of the app.

Mike Corsaro Atlassian Team Aug 16, 2017

Hello! This is probably a bug. Can you upload the "sourcetreeconfig" file in the ".git" directory of the repo that's causing issues? Just to confirm: you're on version

I've checked the sourcetreeconfig file as I read that's where is stores the information. When I add the Stash credentials, it does store in that file.  But somehow Sourcetree is removing the details at some point.  Here's what the file looks like without credentials:


<?xml version="1.0"?>
<RepositoryCustomSettings xmlns:xsd="" xmlns:xsi="">
<DraftCommitMsg />
<string>File Status</string>
<SubtreeLinks />


And after adding the Stash credentials:


<?xml version="1.0"?>
<RepositoryCustomSettings xmlns:xsd="" xmlns:xsi="">
<DraftCommitMsg />
<string>File Status</string>
<SubtreeLinks />


I am not on as that build seems to cause lots of other issues (always tells me i have uncommited changes when I dont, slow UI, slow branch switching, etc.)

Mike Corsaro Atlassian Team Aug 18, 2017

Regarding 2.1.10 perf: can you try the following:

  • Uncheck "Refresh automatically when files change" in options, and uncheck "Refesh when application is not in focus"
  • In run a repo benchmark: Repository->Benchmark Repo Performance and then do the same on 2.1.10.  Then upload those files
  • Try disabling Libgit2 support under the Git options


I unchecked the refresh settings and ran the benchmarks on both of my repos for  The output is below.  I then upgraded to 2.1.10, unchecked the refresh settins again and tried to run the benchmark. It never completes - it has been on "Working copy file status" for several minutes now. I tried on both of my repos and it just gets stuck.  I'll try to let it run for a few more minutes, but I don't think it will complete.

I dont think there's any way to upload non-image files, so I have to copy and paste the benchmark json data:


"GetBranchesMs": 27,
"GetRemoteBranchesMs": 19,
"GetTrackingBranchesForPullMs": 22,
"GetSummaryMs": 488,
"GetTagsMs": 45,
"GetCommitLabelsMs": 120,
"GetStashesMs": 16,
"GetLogsMs": 119,
"GetCommitDetailsMs": 3,
"GetFileStatusAllMs": 434,
"GetRemoteReposMs": 2,
"TotalFiles": 24862,
"HardwareStats": [
"MaxClockSpeed": "3401",
"NumberOfCores": "4",
"NumberOfLogicalProcessors": "8",
"Description": "Intel64 Family 6 Model 94 Stepping 3",
"WMIObjectSearchString": "Select * from Win32_Processor"
"MemoryBytes": "8589934592",
"MemoryGb": "8",
"WMIObjectSearchString": "Select * from Win32_PhysicalMemory"
"BuildNumber": "7601",
"OSDescription": "Microsoft Windows 7 Professional ",
"WMIObjectSearchString": "Select * from Win32_OperatingSystem"
"SourceTreeVersion": "",
"GitVersion": "2.14.1",
"IsSystemGit": true


"GetBranchesMs": 8,
"GetRemoteBranchesMs": 7,
"GetTrackingBranchesForPullMs": 15,
"GetSummaryMs": 1206,
"GetTagsMs": 26,
"GetCommitLabelsMs": 6,
"GetStashesMs": 1,
"GetLogsMs": 45,
"GetCommitDetailsMs": 1,
"GetFileStatusAllMs": 490,
"GetRemoteReposMs": 1,
"TotalFiles": 87794,
"HardwareStats": [
"MaxClockSpeed": "3401",
"NumberOfCores": "4",
"NumberOfLogicalProcessors": "8",
"Description": "Intel64 Family 6 Model 94 Stepping 3",
"WMIObjectSearchString": "Select * from Win32_Processor"
"MemoryBytes": "8589934592",
"MemoryGb": "8",
"WMIObjectSearchString": "Select * from Win32_PhysicalMemory"
"BuildNumber": "7601",
"OSDescription": "Microsoft Windows 7 Professional ",
"WMIObjectSearchString": "Select * from Win32_OperatingSystem"
"SourceTreeVersion": "",
"GitVersion": "2.14.1",
"IsSystemGit": true

Mike Corsaro Atlassian Team Aug 18, 2017

Well, that's not good. Can you send me your log file (you'll have to upload it)? You can find it under:



Additionally, can you uncheck "use libgit2" and try the benchmark again on 2.1.10? Thanks!

Here's the relevant log detail from today:


ERROR [2017-08-11 10:30:29,529] [1] [SourceTree.App] [.ctor] - finish EnsureSquirrelExecutionStubIsCopied
ERROR [2017-08-11 10:30:33,071] [1] [SourceTree.Utils.UpdateHelper] [GetSquirrelStagedUserId] - Couldn't read staging user ID
ERROR [2017-08-11 10:30:33,098] [1] [SourceTree.Utils.UpdateHelper] [GetSquirrelStagedUserId] - Couldn't read staging user ID
ERROR [2017-08-11 10:35:21,791] [1] [SourceTree.App] [.ctor] - finish EnsureSquirrelExecutionStubIsCopied
ERROR [2017-08-11 10:39:59,054] [1] [SourceTree.App] [.ctor] - finish EnsureSquirrelExecutionStubIsCopied
ERROR [2017-08-11 10:45:43,130] [1] [SourceTree.App] [.ctor] - finish EnsureSquirrelExecutionStubIsCopied
ERROR [2017-08-11 13:42:57,773] [1] [SourceTree.App] [.ctor] - finish EnsureSquirrelExecutionStubIsCopied
ERROR [2017-08-11 13:58:12,254] [1] [SourceTree.App] [.ctor] - finish EnsureSquirrelExecutionStubIsCopied
ERROR [2017-08-11 14:08:33,210] [1] [SourceTree.App] [.ctor] - finish EnsureSquirrelExecutionStubIsCopied
ERROR [2017-08-11 14:15:49,817] [1] [SourceTree.App] [.ctor] - finish EnsureSquirrelExecutionStubIsCopied
ERROR [2017-08-17 13:33:48,036] [1] [SourceTree.App] [.ctor] - finish EnsureSquirrelExecutionStubIsCopied
ERROR [2017-08-17 13:33:50,112] [1] [SourceTree.Utils.UpdateHelper] [GetSquirrelStagedUserId] - Couldn't read staging user ID
ERROR [2017-08-17 13:33:50,152] [1] [SourceTree.Utils.UpdateHelper] [GetSquirrelStagedUserId] - Couldn't read staging user ID
ERROR [2017-08-17 15:03:01,295] [1] [SourceTree.App] [.ctor] - finish EnsureSquirrelExecutionStubIsCopied
ERROR [2017-08-18 09:00:06,215] [1] [SourceTree.App] [.ctor] - finish EnsureSquirrelExecutionStubIsCopied
ERROR [2017-08-18 09:16:21,144] [1] [SourceTree.App] [.ctor] - finish EnsureSquirrelExecutionStubIsCopied
ERROR [2017-08-18 11:21:08,104] [1] [SourceTree.App] [.ctor] - finish EnsureSquirrelExecutionStubIsCopied
ERROR [2017-08-18 11:21:10,174] [1] [SourceTree.Utils.UpdateHelper] [GetSquirrelStagedUserId] - Couldn't read staging user ID
ERROR [2017-08-18 11:21:10,215] [1] [SourceTree.Utils.UpdateHelper] [GetSquirrelStagedUserId] - Couldn't read staging user ID

I also checked the box for "Disable LibGit2 integration" and tried to run the benchmarks again. Same issue - it hangs on "Working copy file status".


New entry in the log file:


ERROR [2017-08-18 11:47:26,091] [1] [SourceTree.App] [.ctor] - finish EnsureSquirrelExecutionStubIsCopied

Mike Corsaro Atlassian Team Aug 18, 2017

Can you do the following please:

  • Navigate to "C:\users\USERNAME\AppData\Local\Sourcetree\app-2.1.10\"
  • Open "log4net.config"
  • Change the line "<threshold value="ERROR" />" to "<threshold value="DEBUG" />"
  • Try the benchmark again on 2.1.10 and let it fail
  • Upload the log file

Well even more bizzare, when I changed the log level to DEBUG, the benchmark worked a few times. But I did get it to fail a couple times (along with a couple sucess runs) and grabbed the log files.  There are 4 log files. Hopefully you can access them here:


I also included the benchmarks for both versions.

Thanks, I've narrowed down the issue and created an internal ticket for the bug. A fix for it should be released in the next release. You should change that option back to "ERROR".


Regarding the integration issues: can you try manually adding it? Go to the repo, hit the "settings" button in the toolbar, select the remote repo path, click "edit", and fill in the extended integration options and see if the issue continues.

For the integration issue, what you stated is what I have to do. When I put in the settings manually, they will work for a couple days. Then, for some reason, they are just gone. I'll try to issue a pull request and it will prompt me to add the integration settings.  And it doesn't just happen on my computer. Two other co-workers computers  (both on Windows, version of Sourcetree)  act the same way.


I'm going to try to use 2.1.10 now (as long as the performance is okay) and see if the same thing happens.

The original issue, Sourcetree forgetting my integration settings, happend again this morning using 2.1.10. I went to issue a Pull Request and got the prompt about entering integration settings.

Yesterday, using 2.1.10 as well, I was able to issue a pull request without having to put in the settings (they were already present).

Any update on this? The original issue is still happening on Every time I quit Sourcetree, it forgets the Integration Settings.

Mike Corsaro Atlassian Team Sep 18, 2017

I'm having a hard time reproducing this issue. Does this issue happen on all repos? Additionally, is there anything that you think could be unique to this repo (is it a submodule, etc)?


Just to be clear, the steps to reproduce are:

  • Start Sourcetree, open repo
  • Repo settings -> Edit remote repo
  • Host type: stash, Root URL: blah, Username: blah
  • Hit OK
  • Hit OK again
  • Close Sourcetree
  • Open "{REPO-FOLDER}\.git\sourcetreeconfig"
  • Observe that "RemoteProjectLinks" entry is empty
Like Pavlos Vavolas likes this

This happens with both of the repos I use - which both have the same integration settings.  And both repos have the values removed by the issue observed.

I realize the frustration of saying this, but I also cannot actively reproduce it. I followed the steps you outlined, but the issue does NOT happen.

The only way I've seen it happen (as it did again this morning) is just by happenstance.  I'll be using Sourcetree and creating pull requests one day, and the next day the settings are gone.

I'll try to see if there's any pattern that consistently removes the settings.


Myself and a couple of my coworkers are also having the same exact issue Mark Ross is describing here. The Stash Host URL settings disappear intermittently. When you add them back, they stay there for a few hours to a day or two, then they magically vanish. We've observed this issue in earlier versions as well as the current latest (Windows) version which we are on

Thank you Jawad! I was starting to think it was just me.

I had the same issue happen again this morning (settings disappear) but they were present for several days last week.

I have been having this issue for a while. I have upgraded to version but still am observing the problem. I can't find the pattern to it. The settings will 90% of the time be gone when I log in the morning.

I'm happy to help troubleshoot this as well

I have this exact same problem in Windows 7, for a while now actually. Sourcetree version

Same problem here on v2.3.1.0 and Windows 7.

Please note the settings do not disappear immediately for a given repository.

It's hard to tell what makes it go away though... Some action seems to clear the settings...

I have the exact same problem. It's driving me crazy!

I found a way to reproduce this bug - start SourceTree while the remote repo host is not available (in my case, I did not have a VPN connection to the site where the Stash repo lives). SourceTree gratuitously wipes out the RemoteProjectLink for that repo.

I too have this issue.  It may well be associated with SourceTree not being able to access the repo host.  I work remotely and it seems every time I want to create a pull request on our stash server I have to fill in the extended integration info for the repo again (roughly 2-3 times a week).  I generally only connect to the VPN when I need to push/pull and create PRs, so most of the time SourceTree does not have access to the repo host.

Same issue here. using version Extremely annoying to have to put in the settings multiple times a week.

Same issue for me as well. I'm using Every time I close Sourcetree, optional extended integration settings are wiped out.

We're also on and are having the same problem.
It's also my experience that after losing connection to the repo host.

multiple colleagues are struggling with the same issue, some have given up. its really annoying to have to fill in this value at least once a week

Same thing for me. The steps to reproduce looks the same for me - sometimes SourceTree remembers the settings after exit but usually after a day or two they're gone.


And I'm also using VPN regularly

Hi @Mike Corsaro 

I seem to have this issue in Version 3.3.4, but everytime I restart Sourcetree.
I'm on Windows 10 Enterprise 10 .0.18362 Build 18362 (x64 ). We use Bitbucket Server.

I also have the issue that my new branches not automatically track to the remote one after I push them.

I added the logs here: 

I have the exact same issue on Windows 10 Prof. with SourceTree 3.3.4

Note: run as Administrator is not an option

found this in my logfile

ERROR [2019-12-23 15:41:55,618] [86] [Sourcetree.Analytics.Emau.EMauSubmissionService] [Log] - POST MAU submission FAILED
System.IO.FileLoadException: Die Datei oder Assembly "TimeZoneConverter, Version=, Culture=neutral, PublicKeyToken=null" oder eine Abhängigkeit davon wurde nicht gefunden. Die gefundene Manifestdefinition der Assembly stimmt nicht mit dem Assemblyverweis überein. (Ausnahme von HRESULT: 0x80131040)
Dateiname: "TimeZoneConverter, Version=, Culture=neutral, PublicKeyToken=null"
bei Atlassian.AnalyticsService.Client.Converters.IanaTimezoneConverter.WriteJson(JsonWriter writer, Object value, JsonSerializer serializer)
bei Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeConvertable(JsonWriter writer, JsonConverter converter, Object value, JsonContract contract, JsonContainerContract collectionContract, JsonProperty containerProperty)
bei Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeObject(JsonWriter writer, Object value, JsonObjectContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)
bei Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeObject(JsonWriter writer, Object value, JsonObjectContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)
bei Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.Serialize(JsonWriter jsonWriter, Object value, Type objectType)
bei Newtonsoft.Json.JsonSerializer.SerializeInternal(JsonWriter jsonWriter, Object value, Type objectType)
bei Newtonsoft.Json.JsonConvert.SerializeObjectInternal(Object value, Type type, JsonSerializer jsonSerializer)
bei Sourcetree.Analytics.Emau.EMauSubmissionService.<SubmitBatch>d__62.MoveNext()

@Ana , this problem has returned.  I'm using SourceTree 3.3.8 on Windows 10.  Note, the user that I log in as does not have admin rights on the computer.  I don't know if that's the case for any others that have reported this issue.  It was working fine for me until I upgraded to 3.3.8.  

Now, it just seems to keep wiping out the sourcetreeconfig.json RemoteProjectLinks in the .git folder of my repository.

I already filed a new JIRA ticket for this regression

Like Peter Foti likes this

Do you have a link to the ticket?

Whew - took me a while to figure out out to find it! SRCTREEWIN-12988 

Thanks. Following. In the meantime, I have completely uninstalled 3.3.8, and reinstalled 3.2.6, which was working fine for me.

I'm also seeing this issue in version 3.3.8. I've added a vote and comment to SRCTREEWIN-12988.

2 votes
Mike Corsaro Atlassian Team Jan 18, 2018

Hello everyone! This has been a tough one to debug on our end. To attempt to address the issue, we've made a change that will be rolled out in the 2.5 release. Hopefully this will solve it. 



That is awesome, looking forward to it!

Great! You have no idea how many keyboards you'll save from breaking in despair. :)

Awesome - one of the last big issues on my end since the switch to 2.x

Thanks! Waiting anxiously for it, because this bug is really annoying.


This problem no longer occurs in version (Windows)!

Thanks to all involved!

PS: I'm on Windows 7 x64 and using Bitbucket Server / JIRA Server.

I am not so sure - the issue still occurs for me with version (Windows) - I am on Windows 7 x64 as well.

Yeah, unfortunately the issue still occurs for me too with Windows 7 x64.  Even after running as admin and making the changes.  They hold for 24 hours and then it deletes them.  It's not a big deal to just fix my setting every day.  It's just that it USED to hold and then one day it stopped holding.  I'll be okay.

After update, I worked for two days with no problems, but today the problem came back, like Joe and Jawad reported.

The wait for a fix continues...

Same issue here. Still losing the settings every other day. I'm beyond annoyed when I get to see the message that there's no instance for PRs set after I commit and push. Couldn't you at least tell me before, e.g. when I'm selecting the option to open a PR? That at least would spare me the hassle of opening the PR by hand because I can edit the settings before committing.

Oh, it might be fixed now.  I haven't had to update the settings in a few days.  I can't say for SURE until Monday, but I wanted to leave a positive pre-weekend comment.  Possibly great job, Atlassian Team!  Thanks.

It is definitely NOT fixed. I had to reapply our Stash details this AM. It's a shame Atlassian continues to drag its feet on this issue after all these months.

Mike Corsaro Atlassian Team Jun 08, 2018

Could you try manually downloading the current release:


FWIW "dragging our feet" on this issue is quite the opposite of what we're doing. It's been a very difficult issue to debug as we don't have a reliable way to reproduce it. However, 2.6.0 should hopefully resolve this as the settings file is now saved by using an atomic file write function. Give it a shot and please let us know if you still see issues.

Sorry to have been so harsh; it's just deeply frustrating to keep thinking it's fixed then being disappointed again. And the long-standing severe performance issues some of us are experiencing aren't helping me to feel positive. My efforts to evangelize SourceTree in our development organization basically collapsed as a result of the latter.

PS: I have the new version installed; watch this space...

Mike Corsaro Atlassian Team Jun 08, 2018

Could you email me at ( some additional info (a repo benchmark would help, Repository > Benchmark Repo Performance) so I can help with performance? Thanks!

My settings held over the weekend, so I declare the issue resolved for at least some lucky people.  Thanks, @Mike Corsaroand team!

OK, after a full week 2.6.3 has not lost my Stash settings, so I think you have nailed the problem. Thanks!

That's it!

After update to, this problem no longer occured in past week. I think that it is fixed now.

Thanks to all involved!

After update to, this problem no longer occured in past week. I think that it is fixed now.

Thanks to all involved!

Ana Retamal Atlassian Team Jun 21, 2018

Glad to hear that @lssilveira11! f any of you still encounter this issue, please let us know, we want to help :)



Ana Retamal Atlassian Team Jun 21, 2018

Happy it's working for you too, @Peter Headland!



After upgrading to and now on (Windows), since the last couple of weeks, I have not seen the settings disappear... issue seems to have been resolved. Thanks!

Happening for me and a lot of colleagues in the team.


I'm on Win 10 + Sourcetree



6 months later, after several software updates, the issue still persists. It is very frustrating...

Same for me. Issue is still not fixed in :(

I too am still seeing this as described in the JIRA ticket...   I am on Win10 and Source Tree 3.3.8.    I tried the suggestion as running as Admin, and that didn't work for me.   Basically, it forgets my setting every time I close Source Tree.    I think it may also "forget" when my machine goes to sleep, but I would have to double-check that...

Using v3.3.4.3796 for windows 10 and it is still happening exactly has described in SRCTREEWIN-12912

Using v3.3.8 for Windows and it is still happening as described above.

Microsoft Windows 10 Pro

Using v2.5.5.0 for Windows and it is still happening as described above.

Update to Version 2.6.3 or higher (currently 2.6.9) and the problem seems to be resolved.

Thanks for the hint. I've switched to 2.6.9 and hoping the repo settings will stay for longer time.

I've had the same problems running on Windows 10.

After I've set "Run as Administrator" I've no longer had this problem. My idea is that we need elevation to access the stored details of the remote stash/repo stored on the local machine.

I can now create pull requests from Source Tree instead of having to log onto bitbucket.

Interesting, I'm gonna try it but for me the case was somewhere else - even after the PC restart the settings were there.

Luca Vignaroli found a way to reproduce the issue by setting system date back days - maybe the issue can be diagnosed now:

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events