vscode: Settings sync is suspended due to auth issues, yet signing in again doesn't work

Issue Type: Bug

After updating to the latest version of VSCode, I am now seeing the following error repeatedly on restart:

Settings sync is suspended because of successive authorization failures. Please sign in again to continue synchronizing

Clicking the “Sign In” button shows the list of accounts, and shows my Microsoft account (which I am using for settings sync) as “Signed in”. If I then click my Microsoft account, nothing happens, and the same error is shown again.

I was able to successfully sign out and sign in again, and that seems to have resolved the immediate problem, but something clearly wasn’t in sync–some part of VSCode thought it couldn’t sync, and some other part thought it was signed in successfully.

Mostly filing this as an FYI in case there’s something here that needs to be looked into further.

VS Code version: Code 1.59.0 (379476f0e13988d90fab105c5c19e7abc8b1dea8, 2021-08-04T23:13:12.822Z) OS version: Windows_NT x64 10.0.19043 Restricted Mode: No Remote OS version: Linux x64 5.10.16.3-microsoft-standard-WSL2

System Info
Item Value
CPUs AMD Ryzen 9 3900X 12-Core Processor (24 x 3800)
GPU Status 2d_canvas: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 63.94GB (36.68GB free)
Process Argv –crash-reporter-id 12a7846e-0844-43a9-a018-5c9919bb6fbd
Screen Reader no
VM 0%
Item Value
Remote WSL: Alpine
OS Linux x64 5.10.16.3-microsoft-standard-WSL2
CPUs AMD Ryzen 9 3900X 12-Core Processor (24 x 3800)
Memory (System) 50.16GB (37.80GB free)
VM 0%
Extensions (22)
Extension Author (truncated) Version
remote-containers ms- 0.191.0
remote-ssh ms- 0.65.7
remote-ssh-edit ms- 0.65.7
remote-wsl ms- 0.58.2
vscode-remote-extensionpack ms- 0.21.0
svg-preview Sim 2.8.3
rewrap stk 1.14.0
pestfile xor 0.1.0
npm-intellisense chr 1.4.0
vscode-eslint dba 2.1.23
gitlens eam 11.6.0
vscode-npm-script eg2 0.3.22
json-tools eri 1.0.2
json-pretty-printer eus 1.1.0
vscode-pull-request-github Git 0.29.0
rust-doc-viewer JSc 2.0.1
rust-analyzer mat 0.2.694
git-graph mhu 1.30.0
vetur oct 0.34.1
vscode-coverage-gutters rya 2.8.0
trailing-spaces sha 0.3.1
code-spell-checker str 1.10.2
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
pythonvsuse255:30340121
vscod805:30301674
pythonvspyt200:30340761
vscextlangct:30333562
binariesv615:30325510
vsccppwtct:30329789
pythonvssor306:30344512
bridge0708:30335490
vstre464:30346472

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 8
  • Comments: 20 (13 by maintainers)

Most upvoted comments

Got the same error, even though I was already signed in. The main problem here is it’s not clear what to do with this error, especially that attached Sign in button doesn’t work. All you need to do is to choose an account for Settings Sync (last option, opens browser to sign in).

I had the issue yesterday and the only way to get rid of it was to sign into Github to use Live Share and that made it start working for Settings Sync as well.

Technical correct

In any case, I’m just looking to consolidate so I don’t have to manage two issues. They’re still linked so they’re easy to access from each other.

The person in the other issue has been using insiders, so I chose that one this time.