New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No authentication provider 'microsoft' is currently registered #106321
Comments
(Experimental duplicate detection) |
The SourceMap error does not bug me, I didn't even notice it before looking at the devtools console. |
@carlocardella Can you copy-paste the logs from the output panel with "Microsoft Authentication" selected? This message is shown when trying to refresh the token repeatedly fails, so there is not valid authentication information available. Has anything changed about your network on the machine that shows this? |
No networking changes that I am aware of, and the Stable release on this same machine works fine, the problem is only with Insiders. Here's the output from Insiders:
This is from Stable on the same machine:
|
I was having the same problem for github (i.e. No authentication provider 'github' is currently registered). I was installing the snap package. I removed it and installed the .deb package and works fine with both microsoft and github providers. Hope it helps. |
Thanks, that's interesting to know, unfortunately my problem is on Windows and with a fresh install, no additional extensions, I just run the MSI and launch vscode insiders right after that, no third party extension can cause this as there is none installed |
I investigated this further, I compared a working instance (Stable) and this broken one (Insiders): both issue a POST to
|
I spent some more time inspecting the http requests and responses on the working and bad instances and was finally able to track the problem down to the cached credentials in Windows Credential Manager. I have deleted the two items highlighted and after restarting vscode insiders sync was working again. |
Thanks @carlocardella for the time investigating this! I just pushed a change to automatically delete the stored credentials if we get a bad response back on refresh and show a notification about it. |
Im facing this same issue on PopOs 20.04 ? How do I fix this |
Unable to locate closing commit in issue timeline. You can manually reference a commit by commenting |
Unable to locate closing commit in issue timeline. You can manually reference a commit by commenting |
\closedWith 403a689 |
This bug has been fixed in to the latest release of VS Code Insiders! @carlocardella, you can help us out by confirming things are working as expected in the latest Insiders release. If things look good, please leave a comment with the text Happy Coding! |
I no longer have a repro to confirm the specific problem has gone, anyway I am on the latest insiders and everything is working fine |
On Mac, when I try to sync settings, which requires login first, I get this error: Both of the auto-redirect and manually copy paste generated token did not work. |
@PulsGarney This sounds like a different problem, so I have created a new issue to track it: #108319 |
Okay, Thank you |
Steps to Reproduce:
I see this:
Troubleshooting done so far:
--disable-extensions
--log trace
hoping to find more details in the logsC:\Users\carloc\AppData\Local\Programs\Microsoft VS Code Insiders
C:\Users\carloc\.vscode-insiders
C:\Users\carloc\AppData\Roaming\Code - Insiders
The devtools console shows this:
Seems clear the problem is with this specific installation/machine, but I've not been able to figure out what is wrong.
Interestingly, this Insiders instance was working file last Friday, when I left the machine running untouched through the long weekend and this morning I found it as described.
What else can I try?
The text was updated successfully, but these errors were encountered: