Everything seems to be working fine (i.e. I can commit and push changes), but I have a red exclamation mark on the remote icon. Presuming there's an error I click on it and it opens my Github repository in a browser window - I don't see an error so not sure why it's displaying - can anybody help please?
Facing the same issue here. Did anyone come up with a solution for this ?
If all the push, pull, commits are working but still there is a red exclamation mark on the remote icon and on clicking it you are just redirected to your bit bucket account then the following step can be followed to get rid of the error.
Open Repository from Menu Bar -> Click on Repository Settings -> Edit the origin -> Copy the Remote Origin URL into clipboard -> Remove the origin and paste it again -> Click on Ok.
This somehow refreshes the previous connection and gets rid of the Red Exclamation Mark
PS: Other than the above issue, after updating to 3.3.4 I was also getting invalid credentials error which was fixed by deleting the 'passwd' file in 'C:\Users\<username>\AppData\Local\Atlassian\SourceTree', restarting source tree and entering the credentials while doing a git pull/fetch for connectivity test.
While that worked for me at first, turned out it came back when I closed and re-opened the app. It doesn't seem to keep the correct Remote Account selected in the Repository Settings. Every time I re-start the app, the exclamation point comes back and the "Generic" account is selected. When I set it to my actual remote account the exclamation mark goes away.
I had the same problem since 3.3.8.
Repasting the URL (as per the above answer) didn't work, but I found that on the same screen as the URL the 'Host Type' in the bottom part of the screen was 'unknown'. Changing that to something else made the exclamation go away. (I used Bitbucket)
The section is labelled up as 'Optional extended integration' and then 'Legacy Account Settings' and I am not using it... however changing that host type caused the exclamation to go away, setting it back to unknown caused the exclamation to come back.
Everything seems to be working either way I set it, so I'm leaving it set.
Also confirming that this problem exists on a fresh install of 3.3.8. Setting the BitBucket repository as origin/default and selecting the BitBucket account temporarily resolves it, but as soon as I close and re-open, the account is set back to Generic and the problem returns. Likewise, for Generic accounts for GitHub, the GitHub user account is cleared.
This happened to me since 3.something and continued up till 3.4.4, today. That tip from @Rosie.Coller solvedthe issue for me. Went from "Unknown" to "BitBucket" and got a completely incorrect host URL setup for me as mandatory value but since the actual Git URL is still in place it seems to not make a difference. At least now the irritating red exclamation is gone. Thanks a lot, Rosie. That thing was super annoying!
Thank you for your post. Just spent at least 1 hour trying to solve the exclamation mark. I used version 3.3.4. So I downloaded new SourceTreeSetup - and it's 3.3.6. And all issues magically disappeared.
Not sure why the latest version wasn't offered for upgrade automatically. But I am happy the annoying exclamation mark went away.
I test your solution.
I switch Host Type from Bitbucket to unknown and unknown to Bitbucket and the exclamation go away. But if I restart it the exclamation come back.
I try to put the sourcetreeconfig.json file in .git folder on READ ONLY but Sourcetree use Generic account every restart.
I have 3.3.8 and I'm seeing the exclamation point, too - but not because the repo type is unknown. My repo type setting was GitHub.
A couple of things:
1) editing the entry and then saving does make the exclamation go away but it comes back after restart
2) The type GitHub seems to expect/imply the host name on the url to be www.github.com but the www. part appears to be optional.
3) Clicking on the Remote icon always seems to get me a 404, whether the url says www.github.com or github.com - yet the operations for the branch seem to be working.
We use the Sourcetree 3.3.9 Enterprise MSI version and face the same problem. Just opened a ticket here because when checking out from the local Bitbucket Server instance and the extended repository details are not correct the client also crashes. The symptoms could be easily fixed by switchung to the authenticated local Bitbucket Server account - but these changes are not persisted as described here: https://jira.atlassian.com/browse/SRCTREEWIN-13256
Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...
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
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events