You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which Git host provider are you trying to connect to?
Bitbucket
Can you access the remote repository directly in the browser using the remote URL?
Yes
Expected behavior
I am authenticated and my Git operation completes successfully.
Actual behavior
I was getting following:
fatal: Error converting value {null} to type 'System.Boolean'. Path 'has_2fa_enabled', line 1, position 95.
fatal: Null object cannot be converted to a value type.
followed by password prompt: Password for 'https://***********@bitbucket.org':
instead of being authenticated automatically.
After that, I have set up 2FA for that account, repeated the git pull command, was redirected to browser to perform (two-factor) authentication and authorization, and after that all commands were automatically authenticated.
Git remote format is: https://********@bitbucket.org/*******/*******.git
Hi @nikolazlatkovic thanks for reporting this issue! I believe we've already corrected this issue (#126) and it should be available in the next release. Watch this space 😃
Which version of GCM Core are you using?
2.0.157-beta+b11949c7a5 (macOS, .NET Core 3.1.4)
Which Git host provider are you trying to connect to?
Can you access the remote repository directly in the browser using the remote URL?
Expected behavior
I am authenticated and my Git operation completes successfully.
Actual behavior
I was getting following:
followed by password prompt:
Password for 'https://***********@bitbucket.org':
instead of being authenticated automatically.
After that, I have set up 2FA for that account, repeated the git pull command, was redirected to browser to perform (two-factor) authentication and authorization, and after that all commands were automatically authenticated.
Git remote format is:
https://********@bitbucket.org/*******/*******.git
Logs
The text was updated successfully, but these errors were encountered: