-
Notifications
You must be signed in to change notification settings - Fork 599
after upgrading git for windows today, amazon logon resulted in "NullReference" exception #774
Comments
Shall I try to downgrade? |
the credential in the Credential Vault of Windows of mine should be correct. |
Same issue. Helps only downgrade to version 1.16.3 |
How to downgrade? Shall I just install v1.16.3 or shall I uninstall the newer version first before installing v1.16.3 ? |
The upgrading bringing about this problem is the upgrading of GitForWindows, not the upgrading of GitCredentialManager itself. I don't know whether the upgrading of GitForWin includes the upgrading of GCM. |
I uninstall GCM, and install old. GitForWindows is last version. |
I uninstalled the upgraded GitForWindows(not GCM); I don't know whether the uninstalling of GitForWindows would also uninstall GCM. And then I reinstalled the old version of GitForWindows (I don't know whether the reinstalling would also reinstall GCM). Now every thing works fine. (The NullReferenceException when logging onto amazon now doesn't pop up anymore). So I guess the problems are borne due to the Oct.6th upgrading of GitForWindows. |
the new release Comes with Git Credential Manager v1.18.0. (ignore the first 'comes with'..) |
Same here v1.17.2:
and v1.18.0
|
I installed the previous of version as suggested here and it resolved the issue: git-for-windows/git#1868 (comment)
I did not uninstall the current version. I just ran the installer. |
looking at @viceice report, the difference shown by V1.17.2 is that the creds are for 'basic' with 'NTLM=Auto', but that it never gets that far with V1.18.0. I remember that there was a lot of discussion historically on the Git List about some 'problems' in this area (with libcurl I think), so there is a lot of hackery in that region. Have a look at https://public-inbox.org/git/?q=NTLM+basic+auth to see some on the threads on that issue. With this one https://public-inbox.org/git/alpine.DEB.2.20.1702281116360.3767@virtualbox/ looking like it has a few clues right at the beginning. I suspect that the Cred Manager may also need to be clearer about the reason for the change that is causing the issue (It's beyond my level of knowledge in that arena) |
@nilnul can you verify the issue is fixed in this release https://github.com/Microsoft/Git-Credential-Manager-for-Windows/releases/tag/v1.18.1 |
进入项目的根目录,输入如下命令: git config --global credential.helper store,并在此从远程分支拉取一次代码,即git pull ... |
I was encountering the same NullReferenceException after updating Git for Windows (with the annexed new credential manager), and updating the credential manager to this version fixed it for me. |
@sageliu, Please
I want to verify GCM 1.18.1 is being picked up. |
Windows 10 1803, Git for Windows 2.19.1
Confirming that updating to 1.18.1 fixes it:
In that case, you may want to get the Git for Windows folks to re-release 2.19 with an updated credential manager... |
@jeschu1, great that you guys make such a quick patch. @MrNonsense, thank you for taking that test and it looks assuring. I'll give the new version of GCM a try later for now I'm working in a product environment |
@sageliu ,
to my knowledge, by changing the helper to "store", you may have switched off "manager", aka GCM, which stores password in vault where MS claims safe. |
Like many people in git-for-windows/git#1868 , I downgraded from https://github.com/git-for-windows/git/releases/tag/v2.19.1.windows.1 to https://github.com/git-for-windows/git/releases/tag/v2.19.0.windows.1 (x64 version) which "resolved" the symptom: no more "NullReferenceException" during https pull or push. This narrows down the commit range where the issue was introduced. If you cannot wait for a newer release, try git-for-windows/git#1868 (comment), or try a snapshot, then you can use 1.19.0 as a workaround. |
works great after downgrade to 2.9.0. |
I am getting the same thing.
|
Simply install GCMW >= 1.18.1 after git upgrade. This will resolve this issue. |
I have upgraded git for windows (which, I think, comes with the upgraded git credential manager). Now the upgraded version works fine. Thank you. @jeschu1 |
That should be |
@testworksau: You are right, fixed my comment. 😄 |
Had exactly the same problem .... exactly -> Simply install latest version of GCMW as @testworksau said . So in the system now i have : Git Credential Manager for Windows v1.18.2 What a pain it was typing everytime the passwords .... thank you for this issue :) |
This also fixed the problem for me. Remote is an AWS CodeCommit repo. |
Uh oh!
There was an error while loading. Please reload this page.
It used to work fine as of today, when I clicked the popped out "would you like to upgrade now" button of the git for windows upgrading reminder. (I regret that I just clicked too quick).
Now I face the console window with a "NullReferenceException"; and it prompts me to key in username and password; after I key in the username and password, another NullReferenceException is shown. But astonishingly, git begins enumerating objects and looks normal (with the two exceptions in the heading; see the screenshot below).
I'll try to locate the issue and report any further details.
The text was updated successfully, but these errors were encountered: