After upgrading to 1.95.0, I am logged out of Settings Sync and cannot log in

[kaiyoma]

Type: Bug

After upgrading, I am now seeing a badge on my user profile button, and it says I'm logged out (which I didn't do myself). If I click "Sign in to Sync Settings", nothing seems to happen.

Edit: I was finally able to get the sign-in page to load, and I authenticated successfully, but I'm still seeing the (1) badge on my profile button.

EDIT BY MAINTAINERS: HERE IS A WORKAROUND (YOU MAY NEED TO REPEAT THESES STEPS A FEW TIMES)

• Open the Command Palette (cmd/ctrl+shift+p)
• Run Developer: Reload Window until things work again
  To help us solve the issue, please see After upgrading to 1.95.0, I am logged out of Settings Sync and cannot log in #232516 (comment)

VS Code version: Code 1.95.0 (912bb68, 2024-10-28T20:16:24.561Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item	Value
CPUs	11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (8 x 2995)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	15.71GB (5.67GB free)
Process Argv	--crash-reporter-id 4c14e0ab-6323-4be2-8ea1-b8ae8d1b35aa
Screen Reader	no
VM	0%

Extensions (10)

Extension	Author (truncated)	Version
copy-relative-path	ale	0.0.2
turbo-console-log	Cha	2.10.5
githistory	don	0.6.20
prettier-vscode	esb	11.0.0
gc-excelviewer	Gra	4.2.62
jenkins-declarative-support	jmM	0.1.0
code-groovy	mar	0.1.2
better-folding	Moh	0.5.1
color-highlight	nau	2.8.0
material-icon-theme	PKi	5.12.0

(1 theme extensions excluded)

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
vscrpc:30673769
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
jg8ic977:31013176
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31102340
nativerepl2:31139839
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-t:31132770
wkspc-ranged-t:31151552
cf971741:31144450
iacca2:31156134
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31164048

[TylerLeonhardt]

Do you use GitHub or Microsoft auth with Settings Sync?

Can you follow these steps so that we can get more information on what's going on?

• Open the Command Palette
• Run the Developer: Set Log Level... command
• To the right of Trace, click the double check mark button. ✔️ ✔️ (enables trace logging as the default)
• Wait for the issue to happen...
• Open the Output pane (ctrl+shift+u I think on Windows)
• drop in this issue he contents of the following:
  • Microsoft Authentication or GitHub Authentication Output channel
  • Log (Settings Sync) Output channel
  • Log (Window) Output channel
• Open the Command Palette
• Run the Developer: Set Log Level... command
• To the right of Info, click the double check mark button. ✔️ ✔️ (to set the default back to info)

[kaiyoma]

There's nothing in the Output pane when I try these steps:

vscode-sign-in.mp4

It seems to "think" I'm authenticated, but then it still shows the (1) badge.

[TylerLeonhardt]

So are you trying to use GitHub then?

Also, what does the dropdown in the Output pane say?

[kaiyoma]

So are you trying to use GitHub then?

Yes, I'm authenticating through GitHub.

Also, what does the dropdown in the Output pane say?

[TylerLeonhardt]

So there's nothing in the Settings Sync Output?

And what about GitHub Authentication and Main?

[kaiyoma]

This is all I see under "Settings Sync", even after trying to sign in multiple times:

2024-10-29 16:09:42.385 [info] Using settings sync service https://vscode-sync.trafficmanager.net/
2024-10-29 16:09:42.385 [info] Auto Sync is enabled.
2024-10-29 16:09:42.386 [info] Auto Sync: Suspended until auth token is available.

Nothing relevant under "GitHub" or "Main".

[TylerLeonhardt]

If you sign out of your GitHub account and sign in again, does anything happen?

[TylerLeonhardt]

@sandy081 any thoughts? SteVen was talking to me about a similar issue yesterday.

[kaiyoma]

@TylerLeonhardt I'm already signed out. Attempting to sign in doesn't seem to do anything (no trace messages, no authentication web page, no activity of any kind).

[kaiyoma]

Here's a screencast of what I'm seeing: https://www.youtube.com/watch?v=HgiSn-rrvic

[TylerLeonhardt]

That's very helpful to understand what you're seeing. Thanks! @sandy081 looks like auth isn't getting called by Settings Sync, can you chime in here?

[WangJincheng4869]

After updating the new version, clicking the login button does not respond, and the browser cannot be called to complete the login.

[TylerLeonhardt]

If you downgrade to 1.94 does that work again?
https://code.visualstudio.com/updates/v1_94

[kands-code]

I'm having a similar problem, I can log in fine, but when I close the VSCode and then reopen it, VSCode says I'm logged out and need to log in again. I sync via my GitHub account.

[kands-code]

I have two devices, logged into the same account, and I've noticed that when I log in on one device account, the account on the other device logs out and needs to be logged in again when I close VSCode and then reopen it.

However, it cannot be reliably reproduced, and I am unsure of what is causing it.

[zhanxiaoge]

I encountered this issue after updating today as well. After logging in successfully, it keeps reverting to logged out after a while. I have rolled back to version 1.94.2.

[supergoku1028]

I'm having a similar problem, I can log in fine, but when I close the VSCode and then reopen it, VSCode says I'm logged out and need to log in again. I sync via my GitHub account.

i have this problem too.

[pagunduu]

+1 On this issue. I sign in using my Microsoft account.

Then I Go to a terminal to a directory open it up in code which opens up a new session, it says I need to sign in again to do the sync.

I am more than happy to provide you debug logs if you haven't got them already from users in this issue.

[NoahELE]

I have similar problems, but using the command Developer: Reload Window seems to resolve this.

If I close and reopen VSCode, the Accounts icon menu will say Sign in to Sync Settings. However, reload instead of reopen VSCode makes the sync work again.

[toymil]

I was having this problem minutes ago, but it just resolved itself after I close and reopen vscode for about 5 times ... What???

nvm, the login state will drop after a while.

[pagunduu]

I have similar problems, but using the command Developer: Reload Window seems to resolve this.

If I close and reopen VSCode, the Accounts icon menu will say Sign in to Sync Settings. However, reload instead of reopen VSCode makes the sync work again.

Yep, this somehow fixes the issue.

[TylerLeonhardt]

Talked over this with @sandy081 a bit... our suspicion is that Settings Sync is timing out waiting for auth to be available. The auth comes from the Extension Host... so the machine is slowed down for any reason or if the ExtHost is slowed down for any reason (some heavy extension, for example), then perhaps that is timing out.

This is supported by Developer: Reload Window resolving this - essentially rolling the dice again.

Now, we need your help to narrow down the issue... so I have a couple questions:

1. How many accounts are you logged into in VS Code? (Open the Account menu and tell me how many you see at the top of the menu)
2. We don't have any repro steps that put us into this bad state besides "it just sort of happens" so if you do find some pattern for when this happens, please let us know!
3. Can you follow these steps so that we can get more information on what's going on?
   • Open the Command Palette (cmd/ctrl+shift+p)
   • Run the Developer: Set Log Level... command
   • To the right of Trace, click the double check mark button. ✔️ ✔️ (enables trace logging as the default)
   • Open the Output pane (ctrl+shift+u I think on Windows) and click on the dropdown on the right
   • drop in this issue he contents of the following:
     • Window Output channel
     • Extension Host Output channel

@sandy081 will take a look at this deeper tomorrow morning, but in the meantime the workaround is to:

• Open the Command Palette (cmd/ctrl+shift+p)
• Run Developer: Reload Window until things work again

(I'll include this in the original issue for users to find it)

[manferlo81]

I don't think this is resolved, I am still logged out. It worked right after I updated, but after I closed vscode a couple times it happened again. I'll dig deeper into it and come back with more info...

[HppZ]

It worked right after I updated, but after I closed vscode a couple times it happened again.

1.95.2 not work!

[waiaan]

It worked right after I updated, but after I closed vscode a couple times it happened again.

1.95.2 not work!

the problem still exists

[manferlo81]

Bug is fixed! Thanks Devs.

It's not fixed, you will see after you close vscode a couple of times.

[sandy081]

Yes, this is not fixed completely. As mentioned in the comment, the fix we added is to fix the first case only. With the help of logs (after fixing first case), we found out the root cause for the second case:

• Sign in badge is shown always and nothing seems to happen on signing in or an error is shown that there are no auth providers

Working on providing the fix for this

[iwangbowen]

It's not fixed

[EduardoMay]

It's not fixed

The fix was not implemented in this new update 1.95.2

[maomincoding]

Yes, I have been experiencing this issue since last week, and reinstalling it still causes problems

[CompactProducer]

Why don't you try something to fix this issue? Here's how:

1. Press Ctrl+Shift+X.
2. In the Search Extensions in Marketplace search box, type @Builtin
3. In the Features box, scroll down until you find GitHub Authentication.
4. Right-click GitHub Authentication and click Disable.
5. Again right-click GitHub Authentication and click Enable.
6. In the Features box again, scroll down until you find Microsoft Account.
7. Right-click Microsoft Account and click Disable.
8. Again right-click Microsoft Account and click Enable.

You should now be able to sync your settings.

NOTE: This fix is only temporary, so if you close and re-open Visual Studio Code, the same problem will happen.

[TylerLeonhardt]

Can you all please try the latest insiders build: https://code.visualstudio.com/insiders

It contains the bigger fix for this issue

[CompactProducer]

Can you all please try the latest insiders build: https://code.visualstudio.com/insiders

It contains the bigger fix for this issue

Yep, I can see it's been fixed on the Insiders version, but not on the Stable version.

[albertosantini]

@CompactProducer Need to wait for October 2024 Recovery 3.

[TylerLeonhardt]

Thanks for confirming @CompactProducer. Given the random nature of this bug, I'd love to hear other folks experience as well so that we have the confidence that this is truly squashed.

[CompactProducer]

@CompactProducer Need to wait for October 2024 Recovery 3.

Hopefully, it should be fixed then.

[hAbuMustafa]

Thanks for confirming @CompactProducer. Given the random nature of this bug, I'd love to hear other folks experience as well so that we have the confidence that this is truly squashed.

I just had the same issue, signed out of all accounts to solve and reconnected but got no luck. I just enabled cloud changes, closed VS Code and reopened, and tried to enable settings sync and it worked.

[TylerLeonhardt]

Can you all please try the latest insiders build: https://code.visualstudio.com/insiders

It contains the bigger fix for this issue

[d2kx]

I think there are lot of comments already, just to add my 2 cents: I also have this bug, but I noticed that even on fresh Windows installations (I do them a lot for unrelated reasons), on first fresh start of VSCode I often cannot even sign in because it says there are no authentication providers available. Some reboots and I can sign just fine, however I often start VSCode no longer being signed in then. Started happening with either 1.94 or 1.95 and still applies in 1.95.2. Haven't tried the insider build yet.