Code-settings-sync: Syncing Extensions between systems installs broken extensions

[mariusstrom]

Visual Studio Code Version : 1.19.1
Code Settings Sync Version : 2.8.7
Operating System : Win10.17063
Occurs On: Download
Proxy Enabled: No

Setting up Settings Sync on two machines for the first time. On Machine A, installed sync, installed a number of extensions, uploaded settings.

On Machine B, installed sync, set the Gist, downloaded. Settings Sync indicated it was background installing extensions then a few minutes later the output window popped with success, so I relaunched Code. Extensions appeared to be installed in the Extension Manager (yay!) and the commands for them showed up in command bar (yay!) - but running any of the commands threw an error.

On Machine B, I then uninstalled these extensions (this happened with many extensions), reloaded Code, manually installed them, and it worked fine. I had manually sync'd Machine A and B's extensions.

On Machine B, I then installed a few more extensions. Uploaded, then downloaded onto Machine A. Extensions installed in the background, and the same behavior described above occurred.

[shanalikhan]

can you provide your gist id so i can reproduce that error by installing those extensions?
have you tried on other network or both machines were on same network ?

[mariusstrom]

"sync.gist": "48da6e4769c8b288477fed414caebead"

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Shan [e-mail]
Sent: Wednesday, January 3, 2018 9:08 PM
To: shanalikhan/[e-mail]
Cc: Marius [e-mail]; [e-mail]
Subject: Re: [shanalikhan/code-settings-sync] Syncing Extensions between systems installs broken extensions (#477)

can you provide your gist id so i can reproduce that error by installing those extensions?
have you tried on other network or both machines were on same network ?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/shanalikhan/code-settings-sync/issues/477#issuecomment-355200178, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVZjnfCNMBMj8NOwEUZRQ35zOiRjiD2Eks5tHFy3gaJpZM4RSLCh.

[shanalikhan]

have you tried on other network or both machines were on same network ?

[mariusstrom]

They're on different networks (work, home)

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Shan Khan [e-mail]
Sent: Friday, January 5, 2018 7:09:01 AM
To: shanalikhan/code-settings-sync
Cc: Marius Strom; Author
Subject: Re: [shanalikhan/code-settings-sync] Syncing Extensions between systems installs broken extensions (#477)

have you tried on other network or both machines were on same network ?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/shanalikhan/code-settings-sync/issues/477#issuecomment-355577113, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVZjnUEthtm92ixG6q4CfbZ0iomylqdDks5tHjsNgaJpZM4RSLCh.

[ffxsam]

I'm having similar issues. I just set up a new machine and ran the sync, and the extensions show up as being installed, but they don't work right (or at all). I have to uninstall them, quit VS Code, manually reinstall, quit VS Code, and then it's fine.

EDIT: Not all extensions though. This affected Vetur and Import Cost. Other extensions seem to work OK. So apparently some extensions do not like being installed via whatever method Sync Settings is using.

[FelikZ]

I have missing extensions on one of the hosts.

[daviian]

I ran over the same issue earlier today.
In my case no extension got correctly installed. They were not even listed in the 'Installed Extensions' section.
Had to install all by myself.

[FelikZ]

When I trying to upload settings from Windows hosts - extensions.json appear to be empty in gist. Everything works smooth on linux. How to fix?

[FelikZ]

@mariusstrom seems fixed in 2.9.0, worked for me!

[shanalikhan]

@mariusstrom is it fixed in the latest version, i am still not able to reproduce so far.

[mariusstrom]

sorry for the delay in getting back, it does seem to behave better now!