Gitpod Settings Sync enablement after VS Code Desktop version 1.81

[filiptronicek]

Bug description

After microsoft/vscode#187006, we are not able to sync settings like we used to. We are considering alternative approaches for extensions and settings, but for the time being, users cannot log into Settings Sync in VS Code versions 1.81 and later.

Current workarounds:

• For installing extensions in Gitpod Workspaces automatically, you can use Always Installed Extensions
• You can sync Settings manually by copying them from VS Code Browser to Desktop or vice-versa. You can access the copy-able JSON by looking for the Preferences: Open User Settings (JSON) command inside of the Command Palette (F1).

[Siddhant-K-code]

Related https://github.com/gitpod-io/website/issues/3931

[johndunderhill]

We spent a lot of time running this down in our environment. Initially we thought we had done something wrong, so we removed everything and re-installed and configured from scratch, following the Gitpod documentation exactly, at least twice. The only solution for us was to manually copy the configuration settings to the web interface, and install the necessary extensions in both environments. We now have to maintain this by hand. We've looked at the Microsoft PR that caused this, but we don't really understand what they did or why. Sync is important to us.

[loujaybee]

Thanks for the additional context, @johndunderhill.

I replied on the other issue (https://github.com/gitpod-io/website/issues/3931#issuecomment-1694253393) and closed as duplicate. I'm linking it here also for reference for others. We'll provide more updates as we investigate.

We were also surprised by the VS Code changes are are looking into it. Again, sorry for the disruption, but I'm glad that you found (certainly an imperfect) workaround to get unblocked.

[korpa]

Any news on this?

[akosyakov]

There is no way to integrate with Setting Sync for VS Code Desktop. That's said Gitpod extension will sync your local extensions irregardless.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[tyler36]

Still an issue.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.