"Extension Not Found" prevents download of other extensions
See original GitHub issue🐛 Describe the bug
During sync, if one of the extensions is no longer available, the remaining extensions are not synced.
While syncing extensions.json
-
- Sync Extension A (SUCCESS)
- Sync Extension B (FAILS - extension not found)
- Extention C is not synced
- Extension D is not synced
In the gist, joshpeng.sublime-babel-vscode
is the offending extension. Removing that extension allows the download to work as expected
🌴 Visual Studio Code Version : 1.42.1 🌴 Code Settings Sync Version : 3.4.3 🌴 Standard or Insiders : Standard 🌴 Portable or Installed : Installed 🌴 OSS or Official Build : Official 🌴 Operating System : Linux - Debian 10 🌴 Occurs On: Download 🌴 Proxy Enabled: No 🌴 Gist Id: daafa9b496b8bf332beab39196a7fd17
📰 To Reproduce Steps to reproduce the behavior:
- Start with a fresh install
- Install Sync extension
- Configure Sync extension
- Download Settings
- Error will occur, you’ll need to open developer tools to see the details
💪 Expected behavior
The missing/invalid extension is skipped, and the rest of the extensions.json
file is processed
Optionally it would be good to notify the user exactly which extension is invalid, without requiring them to open the Dev Tools
📺 Console Error Log
[Extension Host] Error: Error: Error: Extension 'joshpeng.sublime-babel-vscode' not found.
at /home/cody/.vscode/extensions/shan.code-settings-sync-3.4.3/out/extension.js:290:22293
at /home/cody/.vscode/extensions/shan.code-settings-sync-3.4.3/out/extension.js:290:11611
at Object.throw (/home/cody/.vscode/extensions/shan.code-settings-sync-3.4.3 out/extension.js:290:11716)
at s (/home/cody/.vscode/extensions/shan.code-settings-sync-3.4.3/out/extension.js:290:10513)
📺 Additional context Issue occurred on a fresh install of VSCode
Issue Analytics
- State:
- Created 4 years ago
- Reactions:29
- Comments:8
Top GitHub Comments
Just go to your gists on GitHub, then find the Visual Studio Code Settings Sync Gist which name can be ‘cloudSettings’ one (I don’t remember details). And all you need is to edit the file ‘extensions.json’.
You can also delete the missing extension from the gist manually.