I'm running macOS Mojave and have recently had to reinstall plugins on VS Code. Live Share has been stuck saying (in the status bar) "Downloading dependencies: Finishing VS Live Share installation..." and won't go away. Live Share is not working.

I'm on VS Code Version 1.33.1 and I have tried uninstalling and then re installing the plugin. Any support appreciated.
To get unblocked, you can try deleting the following folder on your mac: ~\.vscode\extensions\ms-vsliveshare.vsliveshare-1.0.125 (or the equivalent folder if you are running an older extension version), and try installing again.
To help us fix the underlying issue, we can get more information about it from your logs. You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue.
Thanks @dlebu removing that folder fixed it.
Before deleting, when I tried to open the Live Share: Export Logs, it would say Activating Plugin then go back to the Downloading dependencies, so somehow, it was stuck before the plug could properly initialize. Not sure if its a VS issue or an issue with this plugin. Either way, I find it strange that uninstalling the plugin didn't clear the issue.
@mooreaa Glad you got unblocked. You can also get the logs manually at $TMPDIR/VSFeedbackVSRTCLogs.
Attached are my logs. Looks like that should cover pre and post fix.
Thanks for the logs! @setaskin Can you take a look?
I am having the same, or similar issue as the original poster. I tried deleting the extension folder ms-vsliveshare.vsliveshare-1.0.488 out of the way but my VSCode still just hangs with the Source Control side panel with the overlayed clock on it. And it never finishes synchronizing with GitHub, in my case. My VSCode version is 1.33.1 on Windows 10. I run it portably, zip file, no installation although I doubt that is relevant.
I've gone ahead and downloaded v. 1.36 and also running it portably, not an actual install. I copied over all of the extensions and user-data folder from the v. 1.33.1 data folder and when I run v. 1.36 it launches fine and then I am told the extension host has unexpectedly terminated or something to that effect. I choose the option to Restart the Extension Host and things are back to normal and working as they should be.
How does one Restart the Extension Host manually? I am curious to see if doing so in v. 1.33.1 of VSCode will also "unclog" it?
Thank you fellas!
I'm also seeing a similar hang at:
Downloading dependencies...: Finishing VSLS Audio Installation (downloading)...
I tried removing the extension directory and reinstalling, but no dice there.
Here's my system info:
Version: 1.36.1
Commit: 2213894ea0415ee8c85c5eea0d0ff81ecc191529
Date: 2019-07-08T22:55:08.091Z
Electron: 4.2.5
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 4.15.0-54-generic
Extension versions:
Have also tried above steps, but still stuck on "Finishing VS Live Share installation..."
Extension version: 1.0.614
VS Code version: Code - Insiders 1.37.0-insider (92da68a71cfb60bd3b9b0d7fbfb2a7e1fff9dbaf, 2019-08-01T05:33:41.496Z)
OS version: Darwin x64 18.7.0
System Info
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2800)|
|GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_deferred_display_list: disabled_off
skia_renderer: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: disabled_off
webgl: enabled
webgl2: enabled|
|Load (avg)|4, 3, 4|
|Memory (System)|16.00GB (0.23GB free)|
|Process Argv|/Users/satsai/Code/backdraft/backdraft.code-workspace|
|Screen Reader|no|
|VM|0%|
I've encountered the same issue and solved it by uninstalling (rm -rf $HOME/Library/Application\ Support/Code && rm -rf $HOME/.vscode && rm -fr /Applications/Visual\ Studio\ Code.app) and reinstalling VSCode, then adding the live share extension
Like @humbienri mentioned in https://github.com/MicrosoftDocs/live-share/issues/2071#issuecomment-508970359, I too have encountered Extension Host termination on VSCode startup.
However, it occurs every time Live Share gets updated (and even with Live Share Audio disabled) for many months now, and even with Windows 10 x64 (instead of Linux) in my case.
I've detailed this further at microsoft/vscode#80165 and described how this appears to be a trend affecting many extensions and needing some core Extension Host-level fixes, in microsoft/vscode#79782, and the need for extension isolation in microsoft/vscode#52116.
Please upvote and comment on those 3 core VSCode issue reports/requests if believe that this is something that the VSCode core team should prioritize in fixing the root cause (vs. many extension-specific temporary workarounds, considering how many other extensions are affected and the 800+ bug reports across them related to this).
Also comment/upvote if you believe that VSCode should improve logging (so can actually identify the extension causing the crash), auto restart the extension host when occurs, and/or implement extension isolation (like I'd proposed in microsoft/vscode#79782) to avoid crashing all extensions when it does occur.
My logs are stuck at:
[2019-09-17 10:25:43.266 Client I] Passed version check for MacOS: found 18.7.0
[2019-09-17 10:25:43.269 Client I] Installing dependencies for Live Share...
[2019-09-17 10:25:43.270 Client I] Downloading package '.NET Core Runtime 2.2.301 for osx-x64'
I had the same issue with Insiders build on Windows 10. Removing the .vscode-insiders/extensions folder resolved the issue for me.
I'm also stuck. Deleting the folder and reinstalling did not work. The log reads:
[2019-09-20 13:01:37.517 Client I] Passed version check for Linux: found 5.0.0-30-generic
[2019-09-20 13:01:37.531 Client I] Installing dependencies for Live Share...
[2019-09-20 13:01:37.552 Client I] Downloading package '.NET Core Runtime 2.2.301 for linux'
EDIT: I should note I'm using vscode-insiders
Version: 1.39.0-insider
Commit: de03947834d0bcf55093b97c292b76faa75cdebc
Date: 2019-09-23T08:29:46.120Z
Electron: 6.0.9
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Linux x64 5.0.0-30-generic
ANOTHER EDIT: the issue seemingly fixed itself for me. I'm now using
Version: 1.39.0-insider
Commit: 313ede61cbad8f9dc748907b3384e059ddddb79a
Date: 2019-10-01T07:29:26.409Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 5.0.0-30-generic
Same issue. Here is the log.
Untitled.zip
The same issue on Windows 10, appears again even if have deleted .vscode\extension. I have tried using ctrl + shift + p to gain the logs, but the vscode says
Command 'Live Share: Export Logs' resulted in an error (command 'liveshare.exportLogs' not found)
@SaltedFishLZ-870 , please try deleting the global storage location and try installing again. See the comment here: https://github.com/MicrosoftDocs/live-share/issues/180#issuecomment-604074166 . The equivalent folder on windows is [OSdrive]:\Users\[username]\AppData\Roaming\Code\User\globalStorage\ms-vsliveshare.vsliveshare\
Hi
I tried the "delete and reinstall" solution and it didn't work. Still stuck in downloading dependencies.
vs live share parts of json file for user and workspace are :
"liveshare.accountProvider": "microsoft",
"liveshare.account": "my Microsoft email address"
Version: 1.45.1 (user setup)
Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
Date: 2020-05-14T08:27:35.169Z
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19041
log.zip
Same as all the people above
Same issue here, any update?
Installed it on two of my systems, surprisingly, no issue with my Ubuntu system, but facing this issue on my Windows system.
I'm getting:
[2020-08-02 20:26:20.239 LiveShareAudio I] Installing dependencies for VSLS Audio...
[2020-08-02 20:26:20.243 LiveShareAudio I] Downloading package 'electron-win-x64-skype-4.2.7'
Help > About:
Version: 1.47.3
Commit: 91899dcef7b8110878ea59626991a18c8a6a1b3e
Date: 2020-07-23T13:12:49.994Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
Same here.
Here's my system info:
Version: 1.51.1
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-11T01:11:34.018Z (1 wk ago)
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Darwin x64 19.5.0
My live share audio version is v0.1.91
Closing this as a duplicate of #180.
Most helpful comment
Like @humbienri mentioned in https://github.com/MicrosoftDocs/live-share/issues/2071#issuecomment-508970359, I too have encountered Extension Host termination on VSCode startup.
However, it occurs every time Live Share gets updated (and even with Live Share Audio disabled) for many months now, and even with Windows 10 x64 (instead of Linux) in my case.
Related Issues to Upvote for Fixing Root Cause in VS Code
I've detailed this further at microsoft/vscode#80165 and described how this appears to be a trend affecting many extensions and needing some core Extension Host-level fixes, in microsoft/vscode#79782, and the need for extension isolation in microsoft/vscode#52116.
Please upvote and comment on those 3 core VSCode issue reports/requests if believe that this is something that the VSCode core team should prioritize in fixing the root cause (vs. many extension-specific temporary workarounds, considering how many other extensions are affected and the 800+ bug reports across them related to this).
Also comment/upvote if you believe that VSCode should improve logging (so can actually identify the extension causing the crash), auto restart the extension host when occurs, and/or implement extension isolation (like I'd proposed in microsoft/vscode#79782) to avoid crashing all extensions when it does occur.