Git-credential-manager-for-windows: UriFormatException for Git 2.13.1.windows.2

[garretwilson]

Suddenly when I even try to do a simple git pull on repositories I've used for months, with Git version 2.13.1.windows.2 (with GCM enabled) I get:

fatal: UriFormatExceptionencounter.
    actualUrl
Password for 'https://[email protected]':

And it affects my TortoiseGit installation as well, causing it to ask for a password.

After I enter the password in either case, the Git operation succeeds.

I'm using Windows 10 Pro 64-bit with Creator's Update.

Another system is using _netrc, and it does _not_ exhibit this issue.

It's working fine on a GitHub URL in the form https://github.com/example/repo.git. But it's failing for a Bitbucket URL in the form https://[email protected]/example/repo.git.

In Windows Credential Manager, the Bitbucket credentials are showing as "User name: [email protected]". But for GitHub, it's showing as "User name: Personal Access Token". I don't know if difference is significant.

I removed the Bitbucket credentials from Windows Credential Manager. Then I tried git pull again; it failed with the same error, and I had to enter my credentials. This time it added back a new set of credentials to Windows Credential Manager; curiously it now says "User name: user" instead of "User name: [email protected]".

Nevertheless the same thing happens with subsequent pulls: an error message is displayed and I have to manually enter my credentials.

[whoisj]

@garretwilson can you run git credential-manager version and report back the output?

@mminns, from Atlassian, recently fixed a URI formatting bug in the Bitbucket Authority code.

[garretwilson]

It says:

Git Credential Manager for Windows version 1.10.0

[dscho]

Git Credential Manager for Windows version 1.10.0

There has been an update to Git Credential Manager that has not made it into any Git for Windows version yet: 1.10.1. You can install it on top of your existing Git for Windows version without problems. It should fix the reported issue.

[whoisj]

@garretwilson this issue was fixed in v1.10.1, feel free to download and install it over the current version (which came with Git for Windows). Most likely the updated version of the GCM will be picked up by Git for Windows with its next release.

Thanks for reporting the issue.

[garretwilson]

This seems to have been addressed by Git for Windows 2.13.2.windows.1. Thanks.