-
Notifications
You must be signed in to change notification settings - Fork 29.5k
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
Sync settings are invalid after opening a new instance #160500
Comments
Do you see any badges on the account icon or settings gear icon asking you to sign in to sync ? Can you also please provide screenshots of what you see? |
Seems like authentication issue. @TylerLeonhardt Can you please help here to diagnose the issue |
Can you follow these steps so that we can get more information on what's going on?
|
Microsoft Authentication
Log (Window)
Log (Settings Sync)
|
well this is interesting... Can you try in the Insiders version of VS Code and tell me if you see the same? |
Microsoft Authentication
No change in output. |
Let's see if this is a keytar issue then... first log in in vscode (even though it fails) if you have nodejs installed, you can run this simple one-liner to see if the problem is how your keychain is setup:
or if you're on Insiders:
This is using the following open source package: https://github.com/emacs-grammarly/keytar-cli What you should get is something like this: [
{
account: 'github.auth',
password: '....... longggg string ......'
}
]
Additionally, we can see if we can properly set passwords:
and then
should give us that newly created password. |
I get an error that seems to be the same as vscode's log output. |
Ok. This means it's an issue with keytar that we depend on. Let me get an issue going over there and hopefully that team will be able to help more. |
Upstream: atom/node-keytar#472 |
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
ps: See log after a few minutes
ps2: Restarting VS Code also causes sync to pause
The text was updated successfully, but these errors were encountered: