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
Settings sync de-authorized token problem #107287
Comments
Hey @DanaMW, this sounds like #106321. We weren't removing cached credential information when it fails. This should be fixed in the next release, in the meantime can you try manually deleting the credential? If you're on windows, you can open the credential manager, select "Windows Credentials" and then delete "vscode-microsoft.login/account" |
Thank you very much. I see they are similar issues and an update flows inbound now, if I may I will close this in favor of the previous #106321 |
@RMacfarlane Do you know how to find and manually remove this file on mac? I have the exact same issue. |
@Curzey Open "Keychain Access" and look for "vscode-microsoft.login" in the login keychain |
Thanks @RMacfarlane 🎉 - However I only have 'vscode-github.login'. Just for good sake; should it do the trick deleting this? |
I changed my Microsoft user password after having applied an auth token to VS Code for settings syncing. Now I receive log errors as follows:
[2020-09-23 02:31:44.835] [userDataSync] [info] Using settings sync service https://vscode-sync.trafficmanager.net/
[2020-09-23 02:31:44.835] [userDataSync] [info] Auto Sync is enabled.
[2020-09-23 02:31:44.835] [userDataSync] [info] Auto Sync: Suspended until auth token is available.
On the menu it simply states: "Microsoft is currently unavailable". I guess it could be a bug also, but it seems since I have not yet found how to reset it, that it should move you to requesting a new auth token at that click. Or a sub menu to sign out of Microsoft. Since they are not available a sign out option would have fixed this for me. Hope I made this clear enough. Thank you for this fine work.
The text was updated successfully, but these errors were encountered: