The majority of issues in Git Credential Manager for Windows have been fixed in recent versions. After updating SourceTree, go to Tools > Options > Git and click "Update Embedded Git" to get the latest version (at least 2.14.1). I've not seen the issue occur for non-Bitbucket accounts.ĮDIT (): The embedded Git has now been updated, alongside the release of Sourcetree 2.1.11.0. Currently, logging in with your username is still accepted but seems to cause several issues ranging from this repeated login prompt issue to the "too many login attempts" error when pushing. Why doesn't push (or pull) use that same method to authenticate?ĮDIT (20 June 2018): Recent changes to Bitbucket authentication has also meant that you must use your email (NOT your username) when logging in. It seems weird, since I have OAuth for both accounts, and can browse my repos (some of which are private) with no problem. The push was successful, and I saw also that a new entry in "Saved passwords" was created for that repo. That forced the GCM dialog, to which I supplied credentials for the repo that I was pushing to. I removed the Saved passwords that were stored and re-tried a push. Tools > Options > Authentication seemed also to be helpful for me. I agree the GUI is borked since we have no idea for which account or which operation the credintial manager is asking this information. I have had Source Tree 2.x for a long time and don't recall this headache. ![]() The problem seemed to start for me when I added a new bitbucket account (academic) and wanted to use two accounts. I thought I had got the spontaneous dialogs to go away, but they do sometimes re-appear. If it doesn't find a release ( it's not enabled to all users yet), try hold Alt on your keyboard and then click on the Ensure Last Version button to force the upgrade: github-desktop-update-magic.The commands above seemed to help, but not right away. If ☝️ this ☝️ warning doesn't affect you, or you don't mind re-adding all your repos to GitHub Desktop, you can update immediately from the About dialog. I will let you know again when that happens. We will release a new production build soon with Electron v19 that you can update to. This is because those beta and test builds use Electron v19, while the latest 3.0.7 has Electron v17 and won't be able to open the repository database once it's been migrated to Electron v19. They won't be removed from your local disk, don't worry about that, they're just removed from the repository list inside of GitHub Desktop. If you have installed either the latest beta or one of the test builds I shared (3.0.7-test1 and 3.0.7-test2), DO NOT install 3.0.7 unless you don't mind losing your repositories on GitHub Desktop and re-adding them there. Hi all! We just released 3.0.7 with the fix a few hours ago. T09:26:28.591Z - error: `git -c credential.helper= fetch -progress -prune origin` exited with an unexpected code: 128. T09:26:28.591Z - info: Executing fetch: git -c credential.helper= fetch -progress -prune origin (took 1.431s) Check the documentation of your repository hosting service.) If you used username / password authentication, you might need to use a Personal Access Token instead of your account password. ![]() ![]() If you use SSH authentication, ensure the host key verification passes for your repository hosting service. If you use SSH authentication, check that your key is added to the ssh-agent and associated with your account. Check the repository settings to confirm you are still permitted to push commits. You do not have permission to access this repository. You may need to log out and log back in to refresh your token. You are not logged in to your account: see File > Options. (The error was parsed as 3: Authentication failed. If you believe this repository exists and you have access, make sure you're authenticated.įatal: unable to access '': The requested URL returned error: 403 Remote: The requested repository either does not exist or you do not have access.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |