fatal: NullReferenceException encountered when interacting with remote
This is new machine with fresh install of Git.
> git --version
git version 2.19.1.windows.1
I cloned repo using https. Every time when I try to talk to remote I get this.
> git pull
fatal: NullReferenceException encountered.
Object reference not set to an instance of an object.
fatal: NullReferenceException encountered.
Object reference not set to an instance of an object.
I tried uninstalling and installing git again. I also cloned same repo to different directory on disk but none of this helped.
When I go to web UI of my BitBucket, there is 2FA enabled. I don't know if this has anything to do with my problem.
git bitbucket
edited Nov 5 at 8:56
Clijsters
2,29211427
asked Nov 5 at 8:24
Piotr Perak
6,81763463
add a comment |
This is new machine with fresh install of Git.
> git --version
git version 2.19.1.windows.1
I cloned repo using https. Every time when I try to talk to remote I get this.
> git pull
fatal: NullReferenceException encountered.
Object reference not set to an instance of an object.
fatal: NullReferenceException encountered.
Object reference not set to an instance of an object.
I tried uninstalling and installing git again. I also cloned same repo to different directory on disk but none of this helped.
When I go to web UI of my BitBucket, there is 2FA enabled. I don't know if this has anything to do with my problem.
git bitbucket
edited Nov 5 at 8:56
Clijsters
2,29211427
asked Nov 5 at 8:24
Piotr Perak
6,81763463
add a comment |
This is new machine with fresh install of Git.
> git --version
git version 2.19.1.windows.1
I cloned repo using https. Every time when I try to talk to remote I get this.
> git pull
fatal: NullReferenceException encountered.
Object reference not set to an instance of an object.
fatal: NullReferenceException encountered.
Object reference not set to an instance of an object.
I tried uninstalling and installing git again. I also cloned same repo to different directory on disk but none of this helped.
When I go to web UI of my BitBucket, there is 2FA enabled. I don't know if this has anything to do with my problem.
git bitbucket
edited Nov 5 at 8:56
Clijsters
2,29211427
asked Nov 5 at 8:24
Piotr Perak
6,81763463
This is new machine with fresh install of Git.
> git --version
git version 2.19.1.windows.1
I cloned repo using https. Every time when I try to talk to remote I get this.
> git pull
fatal: NullReferenceException encountered.
Object reference not set to an instance of an object.
fatal: NullReferenceException encountered.
Object reference not set to an instance of an object.
I tried uninstalling and installing git again. I also cloned same repo to different directory on disk but none of this helped.
When I go to web UI of my BitBucket, there is 2FA enabled. I don't know if this has anything to do with my problem.
git bitbucket
git bitbucket
edited Nov 5 at 8:56
Clijsters
2,29211427
asked Nov 5 at 8:24
Piotr Perak
6,81763463
edited Nov 5 at 8:56
Clijsters
2,29211427
asked Nov 5 at 8:24
Piotr Perak
6,81763463
edited Nov 5 at 8:56
Clijsters
2,29211427
edited Nov 5 at 8:56
Clijsters
2,29211427
edited Nov 5 at 8:56
Clijsters
2,29211427
2,29211427
asked Nov 5 at 8:24
Piotr Perak
6,81763463
asked Nov 5 at 8:24
Piotr Perak
6,81763463
asked Nov 5 at 8:24
Piotr Perak
6,81763463
6,81763463
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The reason for this is that the Git Credential Manager (GCM) that is distributed with Git 2.19.1 needs to be updated.
The release of Git 2.19.1 says:
Comes with Git Credential Manager v1.18.0.
And when we look at GCM 1.18.1 (the next version) release notes:
Fixes Null Reference exceptions when parameters or contentType are not populated
(Edit 23. Nov 2018): As @pgsandstrom says in the comment, Git has released a new version that also contains a newer GCM. You can download it here: Git Releases.
(Rest is old version before 23. Nov 2018))
The interim fix, until Git releases a new version with the updated GCM is to simply install the new version of Git Credential Manager yourself.
So go download the latest version from here and install it and it should fix your issues.
Note that it is not clear to me whether this is a fault introduced by Git (ie. it fails to populate the parameter or contentType), or that it is a fault introduced by GCM. All I know is that Git has not released a new version that fixes the issue but GCM has.
answered Nov 5 at 8:35
Lasse Vågsæther Karlsen
287k82519717
I chose the wrong account at the first prompt and was never able to recover until I found this post. Not sure if that was the root cause or not but in case it helps someone else.
– No Refunds No Returns
Nov 11 at 2:37
1
Helped me a lot. Thanks.
– Shocky2
Nov 12 at 13:06
It is now sufficient to only update Git, as a version with newer version of GCM has been released.
– pgsandstrom
Nov 22 at 9:05
1
@pgsandstrom Nice, thanks, update-time then :) Also edited the answer.
– Lasse Vågsæther Karlsen
Nov 23 at 7:28
Spot on, was annoying me for days. Upgraded to: git version 2.19.2.windows.1
– GBGOLC
Dec 6 at 23:12
add a comment |
I'm running the newest git version 2.19.1.windows.1 installed via Scoop.
We have migrated repository from GitLab to BitBucket, then I've got the same message:
fatal: NullReferenceException encountered. Object reference not set
to an instance of an object.
What solved the problem was this command:
git config --global credential.helper wincred
answered Dec 4 at 7:40
mpro
1,116619
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53150690%2ffatal-nullreferenceexception-encountered-when-interacting-with-remote%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The reason for this is that the Git Credential Manager (GCM) that is distributed with Git 2.19.1 needs to be updated.
The release of Git 2.19.1 says:
Comes with Git Credential Manager v1.18.0.
And when we look at GCM 1.18.1 (the next version) release notes:
Fixes Null Reference exceptions when parameters or contentType are not populated
(Edit 23. Nov 2018): As @pgsandstrom says in the comment, Git has released a new version that also contains a newer GCM. You can download it here: Git Releases.
(Rest is old version before 23. Nov 2018))
The interim fix, until Git releases a new version with the updated GCM is to simply install the new version of Git Credential Manager yourself.
So go download the latest version from here and install it and it should fix your issues.
Note that it is not clear to me whether this is a fault introduced by Git (ie. it fails to populate the parameter or contentType), or that it is a fault introduced by GCM. All I know is that Git has not released a new version that fixes the issue but GCM has.
answered Nov 5 at 8:35
Lasse Vågsæther Karlsen
287k82519717
I chose the wrong account at the first prompt and was never able to recover until I found this post. Not sure if that was the root cause or not but in case it helps someone else.
– No Refunds No Returns
Nov 11 at 2:37
1
Helped me a lot. Thanks.
– Shocky2
Nov 12 at 13:06
It is now sufficient to only update Git, as a version with newer version of GCM has been released.
– pgsandstrom
Nov 22 at 9:05
1
@pgsandstrom Nice, thanks, update-time then :) Also edited the answer.
– Lasse Vågsæther Karlsen
Nov 23 at 7:28
Spot on, was annoying me for days. Upgraded to: git version 2.19.2.windows.1
– GBGOLC
Dec 6 at 23:12
add a comment |
The reason for this is that the Git Credential Manager (GCM) that is distributed with Git 2.19.1 needs to be updated.
The release of Git 2.19.1 says:
Comes with Git Credential Manager v1.18.0.
And when we look at GCM 1.18.1 (the next version) release notes:
Fixes Null Reference exceptions when parameters or contentType are not populated
(Edit 23. Nov 2018): As @pgsandstrom says in the comment, Git has released a new version that also contains a newer GCM. You can download it here: Git Releases.
(Rest is old version before 23. Nov 2018))
The interim fix, until Git releases a new version with the updated GCM is to simply install the new version of Git Credential Manager yourself.
So go download the latest version from here and install it and it should fix your issues.
Note that it is not clear to me whether this is a fault introduced by Git (ie. it fails to populate the parameter or contentType), or that it is a fault introduced by GCM. All I know is that Git has not released a new version that fixes the issue but GCM has.
answered Nov 5 at 8:35
Lasse Vågsæther Karlsen
287k82519717
I chose the wrong account at the first prompt and was never able to recover until I found this post. Not sure if that was the root cause or not but in case it helps someone else.
– No Refunds No Returns
Nov 11 at 2:37
1
Helped me a lot. Thanks.
– Shocky2
Nov 12 at 13:06
It is now sufficient to only update Git, as a version with newer version of GCM has been released.
– pgsandstrom
Nov 22 at 9:05
1
@pgsandstrom Nice, thanks, update-time then :) Also edited the answer.
– Lasse Vågsæther Karlsen
Nov 23 at 7:28
Spot on, was annoying me for days. Upgraded to: git version 2.19.2.windows.1
– GBGOLC
Dec 6 at 23:12
add a comment |
The reason for this is that the Git Credential Manager (GCM) that is distributed with Git 2.19.1 needs to be updated.
The release of Git 2.19.1 says:
Comes with Git Credential Manager v1.18.0.
And when we look at GCM 1.18.1 (the next version) release notes:
Fixes Null Reference exceptions when parameters or contentType are not populated
(Edit 23. Nov 2018): As @pgsandstrom says in the comment, Git has released a new version that also contains a newer GCM. You can download it here: Git Releases.
(Rest is old version before 23. Nov 2018))
The interim fix, until Git releases a new version with the updated GCM is to simply install the new version of Git Credential Manager yourself.
So go download the latest version from here and install it and it should fix your issues.
Note that it is not clear to me whether this is a fault introduced by Git (ie. it fails to populate the parameter or contentType), or that it is a fault introduced by GCM. All I know is that Git has not released a new version that fixes the issue but GCM has.
answered Nov 5 at 8:35
Lasse Vågsæther Karlsen
287k82519717
The reason for this is that the Git Credential Manager (GCM) that is distributed with Git 2.19.1 needs to be updated.
The release of Git 2.19.1 says:
Comes with Git Credential Manager v1.18.0.
And when we look at GCM 1.18.1 (the next version) release notes:
Fixes Null Reference exceptions when parameters or contentType are not populated
(Edit 23. Nov 2018): As @pgsandstrom says in the comment, Git has released a new version that also contains a newer GCM. You can download it here: Git Releases.
(Rest is old version before 23. Nov 2018))
The interim fix, until Git releases a new version with the updated GCM is to simply install the new version of Git Credential Manager yourself.
So go download the latest version from here and install it and it should fix your issues.
Note that it is not clear to me whether this is a fault introduced by Git (ie. it fails to populate the parameter or contentType), or that it is a fault introduced by GCM. All I know is that Git has not released a new version that fixes the issue but GCM has.
answered Nov 5 at 8:35
Lasse Vågsæther Karlsen
287k82519717
edited Nov 23 at 7:31
answered Nov 5 at 8:35
Lasse Vågsæther Karlsen
287k82519717
answered Nov 5 at 8:35
Lasse Vågsæther Karlsen
287k82519717
answered Nov 5 at 8:35
Lasse Vågsæther Karlsen
287k82519717
287k82519717
I chose the wrong account at the first prompt and was never able to recover until I found this post. Not sure if that was the root cause or not but in case it helps someone else.
– No Refunds No Returns
Nov 11 at 2:37
1
Helped me a lot. Thanks.
– Shocky2
Nov 12 at 13:06
It is now sufficient to only update Git, as a version with newer version of GCM has been released.
– pgsandstrom
Nov 22 at 9:05
1
@pgsandstrom Nice, thanks, update-time then :) Also edited the answer.
– Lasse Vågsæther Karlsen
Nov 23 at 7:28
Spot on, was annoying me for days. Upgraded to: git version 2.19.2.windows.1
– GBGOLC
Dec 6 at 23:12
add a comment |
I chose the wrong account at the first prompt and was never able to recover until I found this post. Not sure if that was the root cause or not but in case it helps someone else.
– No Refunds No Returns
Nov 11 at 2:37
1
Helped me a lot. Thanks.
– Shocky2
Nov 12 at 13:06
It is now sufficient to only update Git, as a version with newer version of GCM has been released.
– pgsandstrom
Nov 22 at 9:05
1
@pgsandstrom Nice, thanks, update-time then :) Also edited the answer.
– Lasse Vågsæther Karlsen
Nov 23 at 7:28
Spot on, was annoying me for days. Upgraded to: git version 2.19.2.windows.1
– GBGOLC
Dec 6 at 23:12
I chose the wrong account at the first prompt and was never able to recover until I found this post. Not sure if that was the root cause or not but in case it helps someone else.
– No Refunds No Returns
Nov 11 at 2:37
I chose the wrong account at the first prompt and was never able to recover until I found this post. Not sure if that was the root cause or not but in case it helps someone else.
– No Refunds No Returns
Nov 11 at 2:37
1
1
Helped me a lot. Thanks.
– Shocky2
Nov 12 at 13:06
Helped me a lot. Thanks.
– Shocky2
Nov 12 at 13:06
It is now sufficient to only update Git, as a version with newer version of GCM has been released.
– pgsandstrom
Nov 22 at 9:05
It is now sufficient to only update Git, as a version with newer version of GCM has been released.
– pgsandstrom
Nov 22 at 9:05
1
1
@pgsandstrom Nice, thanks, update-time then :) Also edited the answer.
– Lasse Vågsæther Karlsen
Nov 23 at 7:28
@pgsandstrom Nice, thanks, update-time then :) Also edited the answer.
– Lasse Vågsæther Karlsen
Nov 23 at 7:28
Spot on, was annoying me for days. Upgraded to: git version 2.19.2.windows.1
– GBGOLC
Dec 6 at 23:12
Spot on, was annoying me for days. Upgraded to: git version 2.19.2.windows.1
– GBGOLC
Dec 6 at 23:12
add a comment |
I'm running the newest git version 2.19.1.windows.1 installed via Scoop.
We have migrated repository from GitLab to BitBucket, then I've got the same message:
fatal: NullReferenceException encountered. Object reference not set
to an instance of an object.
What solved the problem was this command:
git config --global credential.helper wincred
answered Dec 4 at 7:40
mpro
1,116619
add a comment |
I'm running the newest git version 2.19.1.windows.1 installed via Scoop.
We have migrated repository from GitLab to BitBucket, then I've got the same message:
fatal: NullReferenceException encountered. Object reference not set
to an instance of an object.
What solved the problem was this command:
git config --global credential.helper wincred
answered Dec 4 at 7:40
mpro
1,116619
add a comment |
I'm running the newest git version 2.19.1.windows.1 installed via Scoop.
We have migrated repository from GitLab to BitBucket, then I've got the same message:
fatal: NullReferenceException encountered. Object reference not set
to an instance of an object.
What solved the problem was this command:
git config --global credential.helper wincred
answered Dec 4 at 7:40
mpro
1,116619
I'm running the newest git version 2.19.1.windows.1 installed via Scoop.
We have migrated repository from GitLab to BitBucket, then I've got the same message:
fatal: NullReferenceException encountered. Object reference not set
to an instance of an object.
What solved the problem was this command:
git config --global credential.helper wincred
answered Dec 4 at 7:40
mpro
1,116619
answered Dec 4 at 7:40
mpro
1,116619
answered Dec 4 at 7:40
mpro
1,116619
answered Dec 4 at 7:40
mpro
1,116619
1,116619
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53150690%2ffatal-nullreferenceexception-encountered-when-interacting-with-remote%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
