I've been having issues where my coworkers couldn't connect to my share - see #179. I then saw this post, uninstalled the extension and re-installed. My coworker (ticket filer for #179) was then able to connect successfully.

Contents of ~/.vscode/extensions before uninstall:

AravindKumar.gherkin-indent-2.0.0           PeterJausovec.vscode-docker-0.0.25          calebporzio.better-phpunit-0.7.0            eamodio.gitlens-8.1.1                   lukehoban.go-0.6.78                 ms-vscode.cpptools-0.16.0               neilbrayfield.php-docblocker-1.3.3          redhat.vscode-yaml-0.0.10
Arjun.swagger-viewer-1.6.0              PeterJausovec.vscode-docker-0.0.26          castwide.solargraph-0.13.0              eamodio.gitlens-8.2.0                   marcostazi.vs-code-vagrantfile-0.0.7            ms-vscode.cpptools-0.16.1               neilbrayfield.php-docblocker-1.4.0          robinbentley.sass-indented-1.4.8
DavidAnson.vscode-markdownlint-0.14.1           andrejunges.handlebars-0.3.0                castwide.solargraph-0.14.1              felixfbecker.php-debug-1.12.2               mrmlnc.vscode-apache-1.1.1              ms-vsliveshare.vsliveshare-0.2.163          neilbrayfield.php-docblocker-1.6.0          thomas-baumgaertner.vcl-0.1.2
EditorConfig.editorconfig-0.12.1            bajdzis.vscode-twig-pack-1.0.0              christian-kohler.path-intellisense-1.4.2        formulahendry.auto-rename-tag-0.0.15            ms-kubernetes-tools.vscode-kubernetes-tools-0.1.6   msjsdiag.debugger-for-chrome-4.2.1          oderwat.indent-rainbow-0.7.2                vscodevim.vim-0.11.2
HookyQR.beautify-1.3.0                  bmewburn.vscode-intelephense-client-0.8.8       dawhite.mustache-1.1.1                  kumar-harsh.graphql-for-vscode-1.9.1            ms-kubernetes-tools.vscode-kubernetes-tools-0.1.7   msjsdiag.debugger-for-chrome-4.2.2          patrys.vscode-code-outline-0.0.13           vscodevim.vim-0.11.3
KnisterPeter.vscode-github-0.27.1           bungcip.better-toml-0.3.2               donjayamanne.python-0.6.7               lukehoban.go-0.6.77                 ms-vscode.cpptools-0.15.0               msjsdiag.debugger-for-chrome-4.3.0          rebornix.ruby-0.17.0                    whatwedo.twig-1.0.2

Contents of ~/.vscode/extensions after re-install:

AravindKumar.gherkin-indent-2.0.0           PeterJausovec.vscode-docker-0.0.26          castwide.solargraph-0.14.1              formulahendry.auto-rename-tag-0.0.15            ms-kubernetes-tools.vscode-kubernetes-tools-0.1.7   msjsdiag.debugger-for-chrome-4.2.2          rebornix.ruby-0.17.0
Arjun.swagger-viewer-1.6.0              andrejunges.handlebars-0.3.0                christian-kohler.path-intellisense-1.4.2        kumar-harsh.graphql-for-vscode-1.9.1            ms-vscode.cpptools-0.15.0               msjsdiag.debugger-for-chrome-4.3.0          redhat.vscode-yaml-0.0.10
DavidAnson.vscode-markdownlint-0.14.1           bajdzis.vscode-twig-pack-1.0.0              dawhite.mustache-1.1.1                  lukehoban.go-0.6.77                 ms-vscode.cpptools-0.16.0               neilbrayfield.php-docblocker-1.3.3          robinbentley.sass-indented-1.4.8
EditorConfig.editorconfig-0.12.1            bmewburn.vscode-intelephense-client-0.8.8       donjayamanne.python-0.6.7               lukehoban.go-0.6.78                 ms-vscode.cpptools-0.16.1               neilbrayfield.php-docblocker-1.4.0          thomas-baumgaertner.vcl-0.1.2
HookyQR.beautify-1.3.0                  bungcip.better-toml-0.3.2               eamodio.gitlens-8.1.1                   marcostazi.vs-code-vagrantfile-0.0.7            ms-vsliveshare.vsliveshare-0.2.163          neilbrayfield.php-docblocker-1.6.0          vscodevim.vim-0.11.2
KnisterPeter.vscode-github-0.27.1           calebporzio.better-phpunit-0.7.0            eamodio.gitlens-8.2.0                   mrmlnc.vscode-apache-1.1.1              ms-vsliveshare.vsliveshare-0.2.307          oderwat.indent-rainbow-0.7.2                vscodevim.vim-0.11.3
PeterJausovec.vscode-docker-0.0.25          castwide.solargraph-0.13.0              felixfbecker.php-debug-1.12.2               ms-kubernetes-tools.vscode-kubernetes-tools-0.1.6   msjsdiag.debugger-for-chrome-4.2.1          patrys.vscode-code-outline-0.0.13           whatwedo.twig-1.0.2

One surprising oddity that I noticed: when I went to the extensions tab I searched "live share" expecting to see the extension with a gear icon. However it appeared with an install icon. I had to remove my search, uninstall the extension from the list of installed extensions, reload, then install the "VS Live Share" extension again. It appeared as though my local VS Live Share was treated completely independent of the VS Live Share in the marketplace.

codycraven on 5 Apr 2018

In this case where you trying to install/update to 0.2.307?

avanderhoorn on 12 Apr 2018

One surprising oddity that I noticed: when I went to the extensions tab I searched "live share" expecting to see the extension with a gear icon. However it appeared with an install icon. I had to remove my search, uninstall the extension from the list of installed extensions, reload, then install the "VS Live Share" extension again. It appeared as though my local VS Live Share was treated completely independent of the VS Live Share in the marketplace.

Was in the same situation but I don't even see the login button in the status bar. I tried disabling all extensions, uninstalling and reinstalling the share extensions while cleaning up its folder in the extensions folder.
I'm seeing this in vscode insiders but, in regular vscode, where I didn't have the extension installed, it works just fine.
Anything I may need to remove manually in some folder?

posva on 17 Apr 2018

@avanderhoorn I didn't record the version when I performed the update, however looking at my extensions output it does appear to be 0.2.307

codycraven on 18 Apr 2018

We just released v0.2.399 that should provide some improvements in this space. It would be interesting to hear if anyone hits this again with this update.

Chuxel on 18 Apr 2018

My friend is trying to connect to my live server session, and he is using VSC on Linux with the latest version v0.2.399. However, he is still facing this issue:

Error:

Error converting value "local" to type 'Microsoft.Cascade.Contracts.ConnectionMode'. Path '[0].connectionMode'.

Steps to Reproduce:

Connect using sharing link

||Version Data|
|-:|:-|
|extensionName|VSLS|
|extensionVersion|0.2.399|
|protocolVersion|2.1|
|applicationName|VSCode|
|applicationVersion|1.22.2|
|platformName|Linux|
|platformVersion|4.13.0-38-generic|

AkshayKalose on 19 Apr 2018

@AkshayKalose when I encountered this issue it was the host, not the guest that needed an update, what versions is your extension at?

If you do run into this issues, before reinstalling, if you could let us know what VSLS extensions exist in the VS Code install location and what files are any VSLS extension folders that do exist, that would be great!

Windows %USERPROFILE%.vscodeextensions
Mac ~/.vscode/extensions
Linux ~/.vscode/extensions

codycraven on 19 Apr 2018

@codycraven I reinstalled to the latest version of VS Live Share on my computer, and this error disappeared on my friend's computer. Thanks!

I use Windows 10, and here are the extensions I have in my folder (this was after the reinstall / but I assume it should be the same before reinstall since I didn't get any new extensions):
EditorConfig.editorconfig-0.12.1 mikestead.dotenv-1.0.1 PeterJausovec.vscode-docker-0.0.25 ms-python.python-2018.2.1 PeterJausovec.vscode-docker-0.0.26 ms-python.python-2018.3.1 WallabyJs.quokka-vscode-1.0.116 ms-vscode.cpptools-0.15.0 WallabyJs.quokka-vscode-1.0.120 ms-vscode.cpptools-0.16.1 castwide.solargraph-0.14.1 ms-vsliveshare.vsliveshare-0.2.399 castwide.solargraph-0.16.0 octref.vetur-0.11.7 dbaeumer.jshint-0.10.17 rebornix.ruby-0.18.0 dbaeumer.jshint-0.10.18 redhat.java-0.21.0 formulahendry.code-runner-0.9.3 redhat.java-0.23.0 lablup.live-code-runner-4.3.1 ritwickdey.liveserver-3.2.1 lukasz-wronski.ftp-sync-0.3.3

AkshayKalose on 20 Apr 2018

Fresh install today of VS code and Live Share is the only extension so far on this new CentOS computer. Ran into issues with open file limits that kept crashing Live Share so I increased the ulimits and restarted the computer then this starts happening.

dullahan8 on 18 Sep 2018

Any permanent fix yet? I uninstalled and reinstalled, but the error persists.

koredefashokun on 29 Sep 2018

👍3

@korede360 what OS you running? And could you try deleting any live share related extensions from these folders and trying again?

Windows %USERPROFILE%.vscodeextensions
Mac ~/.vscode/extensions
Linux ~/.vscode/extensions

avanderhoorn on 30 Sep 2018

👍4

Worked at first... But no... It's back!

"An update or installation of VS Live Share failed due to a corrupted download. Please uninstall and reinstall the extension to resolve. See https://aka.ms/vsls-corrupted-install for more details."

koredefashokun on 30 Sep 2018

@korede360 Do you know of anything unique or different about your setup that would lead to us having trouble unpacking files?

avanderhoorn on 1 Oct 2018

A friend of mine has the same issue on Windows 7. When he first tried to install the extension, VS Code asked him to install .NET Framework 4.6.1

This took quite a while (~ 20mins) and after that was finished he reloaded VS Code and got the error. After uninstalling the extension, there were still VS Live Share files in the %USERPROFILE%.vscode\extensions directory as mentioned above. He deleted the files, reinstalled the extension and has the same problem.

I hope this is helpful for finding the Issue

Fubinator on 1 Oct 2018

I had a prompt pop up from the extension saying it was corrupted with a link to this issue. However, uninstalling and reinstalling the plugin did not cause it to go away. After some thought and searching around, I suspect that the issue is that my laptop is a 32 bit laptop (running archlinux32) and 32 bit linux does not appear to be a supported architecture for this extension.

You may want to pop up a more informative dialog than 'this extension appears to be corrupted' in that case. Otherwise, if 32 bit linux is intended to be a supported architecture, then it may help to note that in your documentation.

kitlith on 2 Oct 2018

Contents of ~/.vscode/extensions on a mac
alexcvzz.vscode-sqlite-0.3.1 dariofuzinato.vue-peek-1.0.2 dbaeumer.vscode-eslint-1.6.1 dustinsanders.an-old-hope-theme-vscode-3.2.1 eamodio.gitlens-8.5.6 equinusocio.vsc-material-theme-2.4.2 jprestidge.theme-material-theme-1.0.1 letrieu.expand-region-0.1.2 mauve.terraform-1.3.7 mikestead.dotenv-1.0.1 miramac.vscode-exec-node-0.5.0 ms-vscode.cpptools-0.19.0 ms-vscode.go-0.6.91 ms-vsliveshare.vsliveshare-0.3.834 octref.vetur-0.13.0 peterjausovec.vscode-docker-0.3.1 robertohuertasm.vscode-icons-7.27.0 sdras.vue-vscode-snippets-1.3.0 trinm1709.dracula-theme-from-intellij-0.2.7 yummygum.city-lights-theme-1.0.11

BradStell on 17 Oct 2018

I was having this same issue, which I assumed was being caused by my awkward setup. My $VSCODE/User/settings.json and ~/.vscode/extensions folders are both sym-linked from a shared partition on my machine, but a solution above solved it regardless.

For anyone new who encounters this:

Uninstall the extension from the marketplace
Open a new terminal and run cd ~/.vscode/extensions (%USERPROFILE%.vscode\extensions for Windows) to navigate into the containing directory (your directory may live somewhere else if you are an idiot like me who decides to be difficult)
Use the command ls to list the contents of your current directory and then look for "ms-vsliveshare.vsliveshare-x.x.x" (those x's are numbers representing the version)
If nothing matching the above is in your folder, I have no words for you. If it does exist, remove it - on mac and Linux, you just need to type rm -r <the name of the file>.
Reinstall VS Live Share from the marketplace and then reload VSCode, looking for the "Live Share" indicator in the bottom status bar.
Rejoice. Open a beer. And some code.

Tbhesswebber on 9 Feb 2019

👎4 🎉1

Got this issue on Windows 10. I've already joined someone's live session before fine, but now when it tries to update it's saying it's corrupted.

Here's my extensions folder:

MathyFurret on 14 Feb 2019

i simply delete that stuff i am happy that i did not use it and i will use a virtual machine if needed to workaround that no worrys we expect such errors from microsoft only microsoft is able to show a Video when you PC Crashes that says hey your PC Crashed :D

frank-dspeed on 16 Feb 2019

Got this issue on Mac OS Mojave.
Uninstalling/reinstalling did not work.
Here is the content of my extensions folder:

ashiqkiron.gutensnip-1.0.5
dawhite.mustache-1.1.1
dbaeumer.vscode-eslint-1.8.0
digitalbrainstem.javascript-ejs-support-0.4.1
dotjoshjohnson.xml-2.4.0
editorconfig.editorconfig-0.13.0
esbenp.prettier-vscode-1.8.1
espresso3389.insert-file-0.0.2
fabiospampinato.vscode-optimize-images-1.1.0
glen-84.sass-lint-1.0.4
hookyqr.jsdoctagcomplete-0.0.2
ikappas.phpcs-1.0.5
jakebathman.mysql-syntax-1.3.1
mrorz.language-gettext-0.1.1
ms-python.python-2019.1.0
ms-python.python-2019.2.5416
ms-python.python-2019.2.5433
ms-vsliveshare.vsliveshare-0.3.1256
persoderlind.vscode-phpcbf-0.0.8
robinbentley.sass-indented-1.5.1
stevencl.adddoccomments-0.0.8

rdourado on 28 Feb 2019

@rdeltcheva If you delete the ms-vsliveshare.vsliveshare folder and try again does that help?

avanderhoorn on 1 Mar 2019

👍3

https://code.visualstudio.com/docs/editor/extension-gallery

code --uninstall-extension ms-vsliveshare.vsliveshare-pack
code --uninstall-extension ms-vsliveshare.vsliveshare-audio
code --uninstall-extension ms-vsliveshare.vsliveshare
Command Pallete >Developer: Reload Window
Reinstall latest

AndresHurtadoRMT on 10 May 2019

I see this consistently trying to instlal live share on a remote ssh host.

Reinstalling does not work.

eamodio.gitlens-9.9.1
ms-python.python-2019.6.24221
ms-vscode.cpptools-0.24.1
ms-vsliveshare.vsliveshare-1.0.614
mutantdino.resourcemonitor-1.0.6
twxs.cmake-0.0.17
vector-of-bool.cmake-tools-1.1.3

jamescasbon on 31 Jul 2019

ms-python.python-2019.6.24221

you ever get live share to work with remote-ssh?

pkeogan on 13 Aug 2019

I also tried to reinstall it on a Raspberry Pi 2 with Raspbian with Remote Development Extension.
Now a get this issue:
My list of extensions is:

johnpapa.vscode-peacock-3.1.6 ms-vsliveshare.vsliveshare-pack-0.3.4 vscjava.vscode-java-pack-0.8.0 karigari.chat-0.28.0 redhat.java-0.52.0 vscjava.vscode-java-test-0.21.0 ms-vsliveshare.vsliveshare-1.0.1122 visualstudioexptteam.vscodeintellicode-1.2.0 vscjava.vscode-maven-0.19.1 ms-vsliveshare.vsliveshare-1.0.1123 vscjava.vscode-java-debug-0.23.0 ms-vsliveshare.vsliveshare-audio-0.1.66 vscjava.vscode-java-dependency-0.6.0

deinhofer on 6 Nov 2019

I'm getting this issue and I have reinstalled only to be met with the same message.

If you do run into this issues, before reinstalling, if you could let us know what VSLS extensions exist in the VS Code install location and what files are any VSLS extension folders that do exist, that would be great!

I understand the first part of what's in the extensions folder but I'm not sure about the second part. I've got too many extensions to write down but here's a screenshot of all of them.

extensions1
extensions2

DanJ210 on 27 Nov 2019

👍1

I am trying to install the live share on a remote server (I am using remote development pack) and I can't find what I am doing wrong. The remote server is 18.04.3 LTS and Local is OSX Mojave

I only have the Live Share and Remote Development pack extension

Captura de Tela 2019-12-11 às 00 56 10

Edit: Fixed removing all related vscode files in /tmp. For some reason VSCode didn't have permission to change/view some specific files in that folder. So I deleted all and I let vscode creating new files.

Edit2 I think I figure out what happened. I run multiple users (developers) on the same remote server, each one with their own user. Only the first one who enabled the VSCode Live Share after reboot or deleting the VSCode files in /tmp folder is able to use, even if the Live Share is closed. Only the first use is able to reopen the Live Share again.

Edit3 /tmp files on remote server and not on local machine.

Was I clear enough? English is not my primary language.

andremacola on 11 Dec 2019

🎉3 👍1

Received the popup notification in VSCode today.
Windows 10 Pro 1903 (10.0.18362), VS Code v1.41.1 (user setup).

VSLS folders in %userprofile%.vscodeextensions:

.ms-vsliveshare.vsliveshare-1.0.471                                        ms-vsliveshare.vsliveshare-1.0.1056
ms-vsliveshare.vsliveshare-1.0.1456                                        ms-vsliveshare.vsliveshare-1.0.988
ms-vsliveshare.vsliveshare-audio-0.1.80                                    ms-vsliveshare.vsliveshare-pack-0.3.2
ms-vsliveshare.vsliveshare-pack-0.3.3                                      ms-vsliveshare.vsliveshare-pack-0.3.4

Reinstall of VSLS appears fine so far. No change to the content of the extensions folder.

Sebbs128 on 13 Jan 2020

I also have this problem. I run a remote server that multiple users would like to host live sharing on, but only the first user who tries to install it succeeds. The others get the corrupted download error.

geoffrey4444 on 14 Jan 2020

Edit: Fixed removing all related vscode files in /tmp. For some reason VSCode didn't have permission to change/view some specific files in that folder. So I deleted all and I let vscode creating new files.

Edit2 I think I figure out what happened. I run multiple users (developers) on the same remote server, each one with their own user. Only the first one who enabled the VSCode Live Share after reboot or deleting the VSCode files in /tmp folder is able to use, even if the Live Share is closed. Only the first use is able to reopen the Live Share again.

Hi! I have the exact same problem! My live share has been working fine til yesterday and all of sudden it's not working. What files exactly did you remove from /.tmp?

aracpyon on 15 Jan 2020

I'm having this problem just as of a couple days ago, on Mac, I have these files in that folder:

ms-mssql.mssql-1.8.0                robinbentley.sass-indented-1.5.1
ms-vscode.atom-keybindings-3.0.6        sianglim.slim-0.1.2
ms-vscode.vscode-typescript-tslint-plugin-1.2.3 waderyan.gitblame-3.0.1
ms-vsliveshare.vsliveshare-1.0.1482

I also uninstalled and re-installed the plug-in and getting the same error

JamesLivengood on 16 Jan 2020

@JamesLivengood , which version of Mac are you using ? ( We don't support Sierra) Linking the issue with #3124

Also, your logs may provide us with helpful information. You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue.

setaskin on 16 Jan 2020

@setaskin I'm on Sierra! That must be the issue, I'll upgrade. Here are my logs in case they'd still be useful:
Live Share Logs.zip

JamesLivengood on 16 Jan 2020

👍1

Also on Sierra and running into this issue as well
logs.zip

marcandrewb on 27 Jan 2020

👍1

Edit: Fixed removing all related vscode files in /tmp. For some reason VSCode didn't have permission to change/view some specific files in that folder. So I deleted all and I let vscode creating new files.
Edit2 I think I figure out what happened. I run multiple users (developers) on the same remote server, each one with their own user. Only the first one who enabled the VSCode Live Share after reboot or deleting the VSCode files in /tmp folder is able to use, even if the Live Share is closed. Only the first use is able to reopen the Live Share again.

Hi! I have the exact same problem! My live share has been working fine til yesterday and all of sudden it's not working. What files exactly did you remove from /.tmp?

I cant remember the specific files right now. I just deleted all files. The folder is on remote server and not in your local machine.

andremacola on 27 Jan 2020

Hi all. Reinstall does not help in my case.

VS Code metadata:

Version: 1.41.1
Commit: 26076a4de974ead31f97692a0d32f90d735645c0
Date: 2019-12-18T14:57:51.166Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Darwin x64 16.7.0

I see following logs at Output > Log (Extension Host):

[exthost] [error] Activating extension ms-vsliveshare.vsliveshare failed due to an error:
[exthost] [error] Error: Agent terminated with exit code: 0 and signal null: dyld: lazy symbol binding failed: Symbol not found: _syslog$DARWIN_EXTSN
  Referenced from: /Users/user/.vscode/extensions/ms-vsliveshare.vsliveshare-1.0.1510/dotnet_modules/System.Native.dylib
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _syslog$DARWIN_EXTSN
  Referenced from: /Users/user/.vscode/extensions/ms-vsliveshare.vsliveshare-1.0.1510/dotnet_modules/System.Native.dylib
  Expected in: /usr/lib/libSystem.B.dylib
    at ChildProcess.<anonymous> (/Users/user/.vscode/extensions/ms-vsliveshare.vsliveshare-1.0.1510/out/prod/extension-prod.js:124967:32)
    at ChildProcess.emit (events.js:205:15)
    at maybeClose (internal/child_process.js:1021:16)
    at Socket.<anonymous> (internal/child_process.js:430:11)
    at Socket.emit (events.js:200:13)
    at Pipe.<anonymous> (net.js:586:12)

embarq on 28 Jan 2020

This issue has been closed due to no recent activity. We have made many updates to Live Share since this issue, and incorporated a lot of the feedback. Please re-open the issue if the problem still persists.
Live Share team🎈

fubaduba on 29 Jan 2020

👍1

I just got this issue on macOS Mojave (10.14.6) and VS Code 1.42.0.

Contents of ~/.vscode/extensions before trying uninstall & reinstall:

ahdesign.language-antlers-0.0.4
alefragnani.bookmarks-10.7.0
alefragnani.project-manager-10.10.0
bmewburn.vscode-intelephense-client-1.3.9
britesnow.vscode-toggle-quotes-0.3.2
christian-kohler.npm-intellisense-1.3.0
christian-kohler.path-intellisense-1.4.2
codezombiech.gitignore-0.6.0
coenraads.bracket-pair-colorizer-1.0.61
cssho.vscode-svgviewer-2.0.0
dbaeumer.vscode-eslint-2.0.15
dotjoshjohnson.xml-2.5.0
eamodio.gitlens-10.2.0
ecmel.vscode-html-css-0.2.3
editorconfig.editorconfig-0.14.4
eg2.tslint-1.0.44
felixfbecker.php-debug-1.13.0
felixfbecker.php-intellisense-2.3.14
finico.vscode-theme-sunrise-2.2.0
formulahendry.auto-close-tag-0.5.6
formulahendry.auto-complete-tag-0.1.0
formulahendry.auto-rename-tag-0.1.1
formulahendry.code-runner-0.9.15
gamunu.vscode-yarn-1.7.0
grapecity.gc-excelviewer-2.1.32
gruntfuggly.todo-tree-0.0.167
hookyqr.beautify-1.5.0
hoovercj.vscode-power-mode-2.2.0
ikappas.composer-0.7.1
jakebathman.mysql-syntax-1.3.1
juniormucciolo.drupal-7-snippets-0.0.7
karyfoundation.theme-karyfoundation-themes-20.0.3
knisterpeter.vscode-github-0.30.3
korekontrol.saltstack-0.0.6
liximomo.sftp-1.12.9
mads-hartmann.bash-ide-vscode-1.4.0
marcostazi.vs-code-drupal-0.0.12
mblode.twig-language-2-0.9.0
mehedidracula.php-namespace-resolver-1.1.8
michelemelluso.gitignore-1.0.1
mike-flanigan.daobeam-1.3.12
mikestead.dotenv-1.0.1
momosct.momotheme-1.0.0
mrmlnc.vscode-doiuse-1.6.0
mrmlnc.vscode-scss-0.9.0
ms-azuretools.vscode-docker-0.10.0
ms-vsliveshare.vsliveshare-1.0.1510
neilbrayfield.php-docblocker-2.1.0
nhoizey.gremlins-0.15.1
nickdodd79.gulptasks-1.3.1
nkzq.sass-variables-helper-0.2.0
oderwat.indent-rainbow-7.4.0
pauloamgomes.drupal7-hooks-snippets-0.0.2
pflannery.vscode-versionlens-0.24.0
pkief.material-icon-theme-3.9.2
pkief.material-icon-theme-3.9.3
ramyaraoa.sass-helper-0.0.2
redhat.vscode-yaml-0.6.1
ryu1kn.partial-diff-1.4.1
shan.code-settings-sync-3.4.3
shinnn.stylelint-0.51.0
shyykoserhiy.vscode-spotify-3.1.0
sleistner.vscode-fileutils-3.0.1
teamwork.twp-1.0.17
tobiasalthoff.atom-material-theme-1.9.0
wakatime.vscode-wakatime-2.2.1
wakatime.vscode-wakatime-2.3.0
wongjn.php-sniffer-1.2.2
xabikos.javascriptsnippets-1.7.2
zhuangtongfa.material-theme-3.2.2

garrettw on 10 Feb 2020

Issue occurred on Arch Linux on two systems this week.

~/.vscode/extensions

asabil.meson-1.2.0
bbenoist.Nix-1.0.1
bungcip.better-toml-0.3.2
coolbear.systemd-unit-file-1.0.6
davidanson.vscode-markdownlint-0.34.0
dhoeric.ansible-vault-0.1.3
formulahendry.auto-close-tag-0.5.6
foxundermoon.shell-format-7.0.1
ginfuru.ginfuru-vscode-jekyll-syntax-0.1.0
ginfuru.vscode-jekyll-snippets-0.9.1
hangxingliu.vscode-nginx-conf-hint-0.1.0
hookyqr.beautify-1.5.0
ibm.output-colorizer-0.1.2
idleberg.nsis-3.25.0
idleberg.nsis-plugins-1.3.0
idleberg.textile-0.1.5
james-yu.latex-workshop-8.7.1
jinsihou.diff-tool-0.0.1
johnpapa.vscode-peacock-3.3.1
karigari.chat-0.31.0
lextudio.restructuredtext-117.0.0
michaelnewton.textile-preview-1.0.2
ms-azuretools.vscode-cosmosdb-0.12.1
ms-azuretools.vscode-docker-0.10.0
mshr-h.veriloghdl-1.0.4
ms-python.python-2020.1.58038
ms-vscode.azure-account-0.8.8
ms-vscode.cpptools-0.26.3
ms-vscode.powershell-2020.1.0
ms-vscode-remote.remote-containers-0.101.0
ms-vscode-remote.remote-ssh-0.49.0
ms-vscode-remote.remote-ssh-edit-0.49.0
ms-vscode-remote.remote-wsl-0.42.3
ms-vscode-remote.vscode-remote-extensionpack-0.19.0
ms-vsliveshare.vsliveshare-1.0.1510
ms-vsliveshare.vsliveshare-audio-0.1.80
ms-vsliveshare.vsliveshare-pack-0.3.4
panicbit.cargo-0.2.3
redhat.java-0.55.1
rust-lang.rust-0.7.0
searking.preview-vscode-2.0.3
shakram02.bash-beautify-0.1.1
shan.code-settings-sync-3.4.3
shanoor.vscode-nginx-0.6.0
sidneys1.gitconfig-2.0.1
stkb.rewrap-1.9.1
streetsidesoftware.code-spell-checker-1.7.22
timonwong.shellcheck-0.9.0
trixnz.vscode-lua-0.12.4
visualstudioexptteam.vscodeintellicode-1.2.5
vscjava.vscode-java-debug-0.24.0
vscjava.vscode-java-dependency-0.8.0
vscjava.vscode-java-pack-0.8.1
vscjava.vscode-java-test-0.22.1
vscjava.vscode-maven-0.21.0
yzane.markdown-pdf-1.4.1
zignd.html-css-class-completion-1.19.0

Couldn't reinstall it correctly, started receiving warnings again.

After, same versions.

johnramsden on 11 Feb 2020

If you do run into this issues, before reinstalling, if you could let us know …

Here? I guess:

… what VSLS extensions exist in the VS Code install location …

Using ls -1 ~/.vscode/extensions \@ macos10.13.6 (high sierra)

anseki.vscode-color-0.4.5
bmewburn.vscode-intelephense-client-1.3.7
bmewburn.vscode-intelephense-client-1.3.9
coenraads.bracket-pair-colorizer-1.0.61
davidanson.vscode-markdownlint-0.33.0
davidanson.vscode-markdownlint-0.34.0
dbaeumer.vscode-eslint-1.9.1
dbaeumer.vscode-eslint-2.0.15
dotjoshjohnson.xml-2.5.0
eamodio.gitlens-10.2.0
eamodio.gitlens-10.2.1
eg2.tslint-1.0.44
fabiospampinato.vscode-browser-refresh-1.1.5
felixfbecker.php-debug-1.13.0
felixfbecker.php-intellisense-2.3.14
formulahendry.docker-explorer-0.1.6
formulahendry.docker-extension-pack-0.0.1
mads-hartmann.bash-ide-vscode-1.4.0
mikestead.dotenv-1.0.1
mrmlnc.vscode-apache-1.2.0
ms-azuretools.vscode-docker-0.10.0
ms-azuretools.vscode-docker-0.9.0
ms-python.python-2020.1.58038
ms-vscode.cpptools-0.26.3
ms-vscode.cpptools-0.26.3-insiders3
ms-vsliveshare.vsliveshare-0.3.709
ms-vsliveshare.vsliveshare-1.0.1482
ms-vsliveshare.vsliveshare-1.0.1510
octref.vetur-0.12.6
octref.vetur-0.23.0
peterjausovec.vscode-docker-0.2.0
peterjausovec.vscode-docker-0.3.0
royaction.color-manager-0.5.4
symbaslikedef-spirits
vangware.dark-plus-material-2.2.2
vangware.dark-plus-material-2.2.3
waderyan.gitblame-3.0.1

All installed from inside VS Code (VSC), except:
symbaslikedef-spirits, being an old one of mine (non-public) that just "contributes" one little object per {"commands":…, and "keybindings": …}, so I doubt it'd interfere w/ this issue..

vsls-logs200211.zip

My guess on what caused this would be that my cpu stalled during the prev startup of VSC (and subsequent VSLS upgrade/install every startup), and I "force quit" VSC..

After clicking the extension's uninstall, reload, and install buttons, it works opening a link from a friend.

diff'ing the ls -1 after reinstall, the listings are identical.

PS: I didn't really test anything before uninstall, trusting the notification on corruption.

BTW:

@DanJ210 commented on 27 Nov 2019

[…] let us know what VSLS extensions exist in the VS Code install location and what files are any VSLS extension folders that do exist, that would be great!

I understand the first part of what's in the extensions folder but I'm not sure about the second part. […]

I agree.

Peace.

vike2000 on 11 Feb 2020

Reinstalling the previous version fixes it for me on Windows 10.

LayZeeDK on 12 Feb 2020

👍1

Reinstalling extention, reloading window in various configurations, deleting files located at %userprofile%/.vscode/extentions fails to solve the issue. After every step, restarting and deleting and whatnot, installing live share again still results in a link to this page "https://aka.ms/vsls-corrupted-install."
update: The current, latest version of vsls releasted yesterday appears to cause causes this unrepairable and undesirable issue, the developers apparently released a borked version of vsls to the public. Downgrading to the next-latest version solves it instantly in case anyone has issues.

MrSonicMaster on 13 Feb 2020

I'm seeing this in the _Log (Extension Host)_:

[2020-02-13 15:02:28.098] [exthost] [error] Activating extension ms-vsliveshare.vsliveshare failed due to an error:
[2020-02-13 15:02:28.098] [exthost] [error] Error: Agent terminated with exit code: 0 and signal null: A fatal erroroccurred. The required library hostfxr.dll could not be found.
If this is a self-contained application, that library should exist in [c:\Users\marcherm\.vscode\extensions\ms-vsliveshare.vsliveshare-1.0.1587\dotnet_modules\].
If this is a framework-dependent application, install the runtime in theglobal location [C:\ProgramFiles (x86)\dotnet] or use the DOTNET_ROOT(x86) environment variable to specify the runtime location or register the runtime location in [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation].
    at ChildProcess.<anonymous> (c:\Users\marcherm\.vscode\extensions\ms-vsliveshare.vsliveshare-1.0.1587\out\prod\extension-prod.js:128779:32)
    at ChildProcess.emit (events.js:205:15)
    at maybeClose (internal/child_process.js:1021:16)
    at Socket.<anonymous> (internal/child_process.js:430:11)
    at Socket.emit (events.js:200:13)
    at Pipe.<anonymous> (net.js:586:12)

Steps to Reproduce / Scenario:

Start VS Code
See error
An update or installation of VS Live Share failed due to a corrupted download. Please uninstall and reinstall the extension to resolve. See https://aka.ms/vsls-corrupted-install for more details.
Uninstall _Live Share Extension Pack_
Exit VS Code completely
Install _Live Share Extension Pack_
See error
An update or installation of VS Live Share failed due to a corrupted download. Please uninstall and reinstall the extension to resolve. See https://aka.ms/vsls-corrupted-install for more details.

3178, #180

serverhorror on 13 Feb 2020

The Live Share extension is the one that needs to be downgraded. You might need to opt out of the Live Share Extension Pack extension and install them one by one.

LayZeeDK on 13 Feb 2020

Windows %USERPROFILE%.vscodeextensions

Just one correction:
Windows %USERPROFILE%\.vscodeextensions

(it's not a big deal, but if someone try that quickly, will get an error message and might take some time to realize it's just a missing "\".)

brunojuliao on 13 Feb 2020

huh? that looks exactly the same

garrettw on 13 Feb 2020

Thanks for pointing that out @garrettw . It seems that "\" + "." gets parsed as just ".". When I doubled the "\" it show up properly.
EDIT: It happened again with backslash alone... Had to edit and double it to get displayed.

brunojuliao on 13 Feb 2020

@brunojuliao next time use
```
text
```

shows up like this

Windows %USERPROFILE%\.vscode\extension

frank-dspeed on 13 Feb 2020

👍1

/.vscode/extensions

abdelaziz18003.quasar-snippets-1.0.0
af4jm.vscode-m3u-1.0.0
alan.stylus-0.0.4
alefragnani.bookmarks-10.7.0
andys8.jest-snippets-1.7.0
bmewburn.vscode-intelephense-client-1.3.9
brenosolutions.sqlformatter-0.0.7
chaunceykiwi.json-tree-view-2.6.0
christian-kohler.npm-intellisense-1.3.0
christian-kohler.path-intellisense-1.4.2
coenraads.bracket-pair-colorizer-1.0.61
dariofuzinato.vue-peek-1.0.2
dbaeumer.vscode-eslint-2.0.15
digitalbrainstem.javascript-ejs-support-1.3.1
donjayamanne.githistory-0.5.2
dotjoshjohnson.xml-2.5.0
dracula-theme.theme-dracula-2.19.2
dskwrk.vscode-generate-getter-setter-0.5.0
dsznajder.es7-react-js-snippets-2.5.0
eamodio.gitlens-10.2.1
editorconfig.editorconfig-0.14.4
eg2.vscode-npm-script-0.3.11
esbenp.prettier-vscode-3.17.0
esbenp.prettier-vscode-3.20.0
fabianlauer.vs-code-xml-format-0.1.5
firsttris.vscode-jest-runner-0.4.15
formulahendry.auto-close-tag-0.5.6
formulahendry.auto-rename-tag-0.1.1
johnpapa.vscode-peacock-3.3.1
jpoissonnier.vscode-styled-components-0.0.28
kokororin.vscode-phpfmt-1.0.30
mechatroner.rainbow-csv-1.5.0
miramac.vscode-exec-node-0.5.1
ms-azuretools.vscode-docker-0.10.0
ms-ceintl.vscode-language-pack-pt-br-1.42.2
ms-mssql.mssql-1.8.0
ms-vscode.csharp-1.21.11
ms-vscode.vscode-typescript-tslint-plugin-1.2.3
ms-vsliveshare.vsliveshare-1.0.1587
ms-vsliveshare.vsliveshare-pack-0.3.4
naumovs.color-highlight-2.3.0
nickdemayo.vscode-json-editor-0.2.3
nicoespeon.abracadabra-3.2.0
octref.vetur-0.23.0
oliversturm.fix-json-0.1.2
orta.vscode-jest-3.1.1
pkief.material-icon-theme-3.9.3
prograhammer.tslint-vue-1.5.6
quicktype.quicktype-12.0.46
redhat.vscode-yaml-0.7.2
richie5um2.vscode-sort-json-1.18.0
rocketseat.rocketseatreactjs-2.2.0
rocketseat.rocketseatreactnative-2.2.0
sdras.night-owl-1.1.3
sdras.vue-vscode-extensionpack-0.2.0
sdras.vue-vscode-snippets-1.8.0
sequoia.loopback-json-schemas-1.0.0
shan.code-settings-sync-3.4.3
simonmosesonazi.quasar-v1-snippets-1.0.2
sirtori.indenticator-0.6.0
syler.sass-indented-1.7.5
sysoev.language-stylus-1.11.0
telerik.nativescript-0.11.0
tombonnike.vscode-status-bar-format-toggle-2.0.0
tomoki1207.pdf-0.5.1
visualstudioexptteam.vscodeintellicode-1.2.5
wallabyjs.quokka-vscode-1.0.262
wallabyjs.quokka-vscode-1.0.277
wayou.vscode-todo-highlight-1.0.4
wmaurer.vscode-jumpy-0.3.1
xabikos.javascriptsnippets-1.7.2

luisipv7 on 13 Feb 2020

@frank-dspeed also `` around the text, like this

garrettw on 13 Feb 2020

Edit: My bad, I see https://github.com/MicrosoftDocs/live-share/issues/3178 now, disregard

ojintoad on 13 Feb 2020

Good evening,
since today I have this problem:
An update or installation of VS Live Share failed due to a corrupted download. Please uninstall and reinstall the extension to resolve. See https://aka.ms/vsls-corrupted-install for more details.
Can you help me because it is the only way I can follow my lessons.
Thank you

vivi83 on 13 Feb 2020

👍1

@vivi83 Have you read through the replies above and tried suggestions that have worked for others?

garrettw on 13 Feb 2020

@ojintoad You do have the ability to delete your comment if necessary.

garrettw on 13 Feb 2020

It does not work for me either (win10). I had to use the previous version but it causes sync errors with my friend which is using the latest version on a mac.

hornta on 14 Feb 2020

@garrettw , yes i tried but it didn't change anything

vivi83 on 14 Feb 2020

I also ran into this issue. Reinstalling the extension did not help.

I'm on windows 10 and those are all of the vsls extensions that are in my %userprofile%/.vscode/extensions folder.

CodingDive on 14 Feb 2020

I'm still having this issue through a Remote-SSH connection macOS -> linux machine.

Before reinstall:

total 0
drwxr-xr-x 1 jator jator_users 30 Feb  8 16:07 ms-vscode.cmake-tools-1.3.0
drwxr-xr-x 1 jator jator_users 36 Jan 23 17:17 ms-vscode.cpptools-0.26.3
drwxr-xr-x 1 jator jator_users 33 Feb 14 21:25 ms-vsliveshare.vsliveshare-1.0.1615
drwxr-xr-x 1 jator jator_users  7 Feb  6 15:08 waderyan.gitblame-3.0.1

jonator on 20 Feb 2020

👍1

I'm also running into this issue as well. Error message is:

An update or installation of VS Live Share failed due to a corrupted download. Please uninstall and reinstall the extension to resolve. See https://aka.ms/vsls-corrupted-install for more details.

My extensions on VS Code 1.42.1 macOS 10.12.6 are:

bmewburn.vscode-intelephense-client-1.3.11 
formulahendry.vscode-mysql-0.4.0          
junstyle.php-cs-fixer-0.1.129
coenraads.bracket-pair-colorizer-1.0.61    
fwcd.kotlin-0.2.11                         
mathiasfrohlich.kotlin-1.7.1
eamodio.gitlens-10.2.1                     
fwcd.kotlindebug-0.2.4                     
ms-azuretools.vscode-docker-0.10.0
esafirm.kotlin-formatter-0.0.6            
gruntfuggly.todo-tree-0.0.167              
ms-vsliveshare.vsliveshare-1.0.1615
felixfbecker.php-debug-1.13.0              
ikappas.phpcs-1.0.5                        
mtxr.sqltools-0.21.6
felixfbecker.php-intellisense-2.3.14       
akebathman.mysql-syntax-1.3.1             
neilbrayfield.php-docblocker-2.1.0

CKilgoreCB on 21 Feb 2020

I've been trying to install the Live Share extension for two hours now. Before, it was stuck at "Downloading Dependencies: Finishing VS Live Share Installation (Downloading), but now, it "installs, and gives this exact error

An update or installation of VS Live Share failed due to a corrupted download. Please uninstall and reinstall the extension to resolve. See https://aka.ms/vsls-corrupted-install for more details.

This is my extensions-folder:

I've been uninstalling and reinstalling for ages now, and are pretty tired of this now. I need help as soon as possible, preferably today, due to this being necessary for a school project.

DragonaxeYT on 27 Feb 2020

I'm also running into this issue as well:

An update or installation of VS Live Share failed due to a corrupted download. Please uninstall and reinstall the extension to resolve. See https://aka.ms/vsls-corrupted-install for more details.

Have tried completely uninstalling VSCode, and re-installing both VSCode and this plug-in, but it's not making any difference.

gillidandaweb on 28 Feb 2020

👍3

Same.

leandroz on 28 Feb 2020

Workaround: roll back to a previous version of the plug-in.

gillidandaweb on 28 Feb 2020

Workaround: roll back to a previous version of the plug-in.

What version worked for you?

k-y on 4 Mar 2020

I rolled back to 1.0.1615 (20 days ago), it stopped working for me today. I'm using VSCode Insiders tho, but I hope that works for you too.

Also, this is the content of my extensions:

dbaeumer.vscode-eslint-1.9.1
editorconfig.editorconfig-0.14.2
esbenp.prettier-vscode-2.3.0
johnpapa.vscode-peacock-3.1.5
karigari.chat-0.22.1
karigari.chat-0.24.0
ms-vsliveshare.vsliveshare-1.0.950
ms-vsliveshare.vsliveshare-1.0.988
ms-vsliveshare.vsliveshare-audio-0.1.66
ms-vsliveshare.vsliveshare-pack-0.3.3
msjsdiag.debugger-for-chrome-4.12.0
vscode-icons-team.vscode-icons-9.4.0

Erid on 5 Mar 2020

An update or installation of VS Live Share failed due to a corrupted download. Please uninstall and reinstall the extension to resolve. See https://aka.ms/vsls-corrupted-install for more details.

reinstalling did not help and I was denied permission to view my extensions

asiamorozova on 12 Mar 2020

One breadcrumb that hopefully shines some light on the issue: I consistently get this error across the most recent versions after server uninstall/install cycles. It did work once (and only once), however:

Restarting my machine. I reloaded the window, and it went back to crashing due to corrupted intsall.

seanders on 12 Mar 2020

Just had this problem installing the Live Share extension. Files that existed in .vscodeextensions before reinstallation:

03/14/2020  04:52 PM    <DIR>          .
03/14/2020  04:52 PM    <DIR>          ..
03/14/2020  04:52 PM                44 .obsolete
01/07/2020  10:01 PM    <DIR>          clarkyu.vscode-sql-beautify-0.1.12
10/24/2019  12:09 AM    <DIR>          jakebathman.mysql-syntax-1.3.1
03/03/2020  12:31 PM    <DIR>          mgmcdermott.vscode-language-babel-0.0.26
03/14/2020  04:50 PM    <DIR>          ms-vsliveshare.vsliveshare-1.0.1742
           1 File(s)             44 bytes

kmoser on 15 Mar 2020

I just had this issue as well, here is the contents of my extension folder when this happed.

adamcaviness.theme-monokai-dark-soda-0.0.6        dunstontc.dark-plus-syntax-0.0.163                justjavac.vscode-deno-1.4.0                       rokoroku.vscode-theme-darcula-1.2.0
akamud.vscode-theme-onedark-2.2.0                 eamodio.gitlens-10.2.1                            kumar-harsh.graphql-for-vscode-1.15.3             rust-lang.rust-0.7.0
alexkrechik.cucumberautocomplete-2.14.1           eg2.vscode-npm-script-0.3.11                      ms-azuretools.vscode-docker-1.0.0                 ryanluker.vscode-coverage-gutters-2.4.3
amazonwebservices.aws-toolkit-vscode-1.7.0        equinusocio.vsc-community-material-theme-1.4.1    ms-dotnettools.csharp-1.21.14                     sainnhe.gruvbox-material-6.0.1
andys8.jest-snippets-1.8.0                        equinusocio.vsc-material-theme-32.5.0             ms-mssql.mssql-1.9.0                              uloco.theme-bluloco-dark-3.0.1
bungcip.better-toml-0.3.2                         equinusocio.vsc-material-theme-icons-1.1.4        ms-python.python-2020.2.64397                     vangware.dark-plus-material-2.2.3
coenraads.bracket-pair-colorizer-1.0.61           esbenp.prettier-vscode-3.20.0                     ms-vsliveshare.vsliveshare-1.0.1742               vscodevim.vim-1.13.0
dart-code.dart-code-3.8.1                         ginfuru.ginfuru-better-solarized-dark-theme-0.9.3 oderwat.indent-rainbow-7.4.0                      zhuangtongfa.material-theme-3.2.3
dart-code.flutter-3.8.1                           hookyqr.beautify-1.5.0                            orta.vscode-jest-3.1.1
dbaeumer.vscode-eslint-2.1.1                      jonsmithers.open-in-vim-0.6.0                     patricklee.vsnotes-0.7.1

Deadairx on 16 Mar 2020

Same issue when I try to open the session about the vscode providing invitation popup. But as my collegue sent me the invitation by the weblink, it worked 🤷‍♂

beatgrabe on 17 Mar 2020

I have done that, installed and restarted vs code but it does not work on the latest version, I still have to go back to v1.0.1510.

It seems like any later version than that will just give me this error when loading VS code.
I also cannot click on any of the links like "join collaboration session..." "Start collaboration session..." and "start read-only collaboration session". If I click on them, it just highlights the text but it does nothing else.

Is there anything else I can do to fix this?

LukeWolfGames on 19 Mar 2020

👍1

I had the same issue on a Mac. Re-install, restart, etct didn't work. Eventually I was able to resolve the issue on my machine.

In VS code I opened the dev tools console to check for any errors. This is what I found:
afbeelding

I then installed the latest dotnet core version, but that didn't help.

Looking into the ../globalStorage/ms-liveshare.vsliveshare/ folder, I found two dotnet folders: dotnet-3.0.0 & dotnet-3.1.1.

Two resolve the issue, I deleted the dotnet-3.1.1 folder and restarted VS code

jeroenschieven on 24 Mar 2020

👍2 🎉1

Reverting back to version 1.0.1510 looks like it has worked for me. Thanks @LukeWolfGames

I'm on Mojave 10.14.6

priyesh86 on 24 Mar 2020

🎉1

is there any way to back into the previous release?

and this my last log of live share.

Aldiwildan77 on 24 Mar 2020

Bring up your extensions in the sidebar and choose "Install another version" from the Live Share settings menu.

gillidandaweb on 24 Mar 2020

reactivating the issue since we started to see the problem again. cc @BrunoGuardia

setaskin on 24 Mar 2020

❤1 👍1

ahh, this worked for me and thanks for the solution I changed it to 1.0.1653 version @gillidandaweb

Aldiwildan77 on 24 Mar 2020

This is happening to my team. We are trying to host live sessions that are installed on a linux machine through the remote ssh extension. I don't know if that has anything to do with this problem

jonator on 24 Mar 2020

Edit2 I think I figure out what happened. I run multiple users (developers) on the same remote server, each one with their own user. Only the first one who enabled the VSCode Live Share after reboot or deleting the VSCode files in /tmp folder is able to use, even if the Live Share is closed. Only the first use is able to reopen the Live Share again.

Edit3 /tmp files on remote server and not on local machine.

We are having this same problem. Deleting /tmp files isn't really a fix as only the first user to install after the delete is able to use Live Share. Want the ability to have many users running Live Share extension.

bmfisher on 24 Mar 2020

It's interesting how you guys can go above version v1.0.1510 and not experience this issue because for me, I tried every version above this one and it will not respond.

I had the same issue. Re-install, restart, etct didn't work. Eventually I was able to resolve the issue on my machine.

In VS code I opened the dev tools console to check for any errors. This is what I found:

I then installed the latest dotnet core version, but that didn't help.

Looking into the ../globalStorage/ms-liveshare.vsliveshare/ folder, I found two dotnet folders: dotnet-3.0.0 & dotnet-3.1.1.

Two resolve the issue, I deleted the dotnet-3.1.1 folder and restarted VS code

@jeroenschieven Interesting. Can you please be more specific about how you resolved this issue? I cannot see a globalStorage folder anywhere with ms-liveshare.vsliveshare in it? The only folder that I have for ms-liveshare.vsliveshare is inside the .vscodeextensions directory in C:\users[username].vscodeextensions

Can you please detail step by step how you resolved the issue?

LukeWolfGames on 24 Mar 2020

I had the same issue on a Mac. Re-install, restart, etct didn't work. Eventually I was able to resolve the issue on my machine.

In VS code I opened the dev tools console to check for any errors. This is what I found:

I then installed the latest dotnet core version, but that didn't help.

Looking into the ../globalStorage/ms-liveshare.vsliveshare/ folder, I found two dotnet folders: dotnet-3.0.0 & dotnet-3.1.1.

Two resolve the issue, I deleted the dotnet-3.1.1 folder and restarted VS code

@jeroenschieven Thank you. Deleting this folder works for me!

@LukeWolfGames on a mac you have to go to $HOME/Library/Application Support/Code/User/globalStorage/ms-vsliveshare.vsliveshare and there is the dotnet-3.1.1 folder.

MJECloud on 25 Mar 2020

❤2 🚀1

@MJECloud Oh, I'm not on a Mac so how do I do that on Windows or is it different?

LukeWolfGames on 26 Mar 2020

@LukeWolfGames i think i've find the folder on windows: C:\Users\USER_NAME\AppData\Roaming\Code\User\globalStorage\ms-vsliveshare.vsliveshare
There you have to delete the dotnet-3.1.1 folder.
USER_NAME is your user folder.

MJECloud on 26 Mar 2020

❤1

@MJECloud your advice worked!

1) Follow advice from @MJECloud.
2) Update LiveShare to the latest if you have not yet.
3) Restart vscode.
4) If you cannot start a collaboration session properly, click on the liveshare options along the status bar that runs along the bottom of vscode. It will drop down some options along the top.
5) Sign out.
6) Repeat step 4 and choose to sign in.

The liveshare side-tab will show you (and other contacts) offline but you can now run a liveshare session by creating a session link. Currently, I am not sure if the status of the contacts list will change later/after the session but I've known it to do that in these circumstances on earlier versions.

LukeWolfGames on 27 Mar 2020

🎉2

I was getting this in the console, even after an uninstall. The plugin was reinstalling itself. I uninstalled several times. The folder it complained about did not exist at the time.

Error: Error: deleting: Unable to delete the existing folder '/Users/HOME/.vscode/extensions/ms-vsliveshare.vsliveshare-1.0.1847' while installing the extension 'ms-vsliveshare.vsliveshare'. Please delete the folder manually and try again

jeremygaither on 30 Mar 2020

@jeremygaither Try going to that directory and deleting the folder by right clicking on it and clicking "delete".

LukeWolfGames on 30 Mar 2020

Got this running Windows 10 Pro (10.0.18362)
VS Code Version 1.43.2 (system setup)

Re-install didn't fix

Directory in question contains the following (same before and after re-install).

04/01/2020 11:44 AM

.
04/01/2020 11:44 AM ..
04/01/2020 11:44 AM johnpapa.vscode-peacock-3.6.0
04/01/2020 11:44 AM karigari.chat-0.33.0
04/01/2020 11:44 AM ms-vsliveshare.vsliveshare-1.0.1891
04/01/2020 11:44 AM ms-vsliveshare.vsliveshare-audio-0.1.80
04/01/2020 11:43 AM ms-vsliveshare.vsliveshare-pack-0.3.4

jwilliamsnephos on 1 Apr 2020

The directory in the error message did not exist as far as I could tell.

On Mar 30, 2020, at 2:45 PM, Luke Wolf notifications@github.com wrote:

@jeremygaither Try going to that directory and deleting the folder by right clicking on it and clicking "delete".

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

jeremygaither on 1 Apr 2020

It seems that Live Share works best sharing local files

We are using Live Share locally after linking github account!

In my scenario we're wanting to use VS Code with the Remote - SSH extension. Editing files on the remote host directly in VS Code through the SSH tunnel.
We then were thinking it would be nice to use the Live Share extension.... and have not been successful running from the server this way.

We can install the Live Share when connected to the server using Remote SSH extension, the extension option to install shows

"This extension is enabled on 'SSH: myhost' "

When I am disconnected from the server the extension option to install shows

"This extension is enabled globally."

We can use Live Share locally after linking github account!
We cannot use Live Share remotely. Immediately after connecting to myhost in VS Code this little popup in the bottom right corner:

"An update or installation of VS Live Share failed due to a corrupted download. Please uninstall and reinstall the extension to resolve. See https://aka.ms/vsls-corrupted-install for more details."

I was watching the logs on the server hoping to identify a problem... ~/.vscode-server/data/logs/20200401T154832/remoteagent.log
.
[2020-04-01 15:59:18.871] [remoteagent] [info] [127.0.0.1][50f785bc][ManagementConnection] New connection established. [2020-04-01 15:59:18.872] [remoteagent] [info] [127.0.0.1][2db7f047][ExtensionHostConnection] New connection established. [2020-04-01 15:59:18.879] [remoteagent] [info] [127.0.0.1][2db7f047][ExtensionHostConnection] <56970> Launched Extension Host Process. [2020-04-01 16:04:15.531] [remoteagent] [info] New EH opened, aborting shutdown [2020-04-01 16:13:07.265] [remoteagent] [info] Installing extension: ms-vsliveshare.vsliveshare [2020-04-01 16:13:08.350] [remoteagent] [info] Downloaded extension: ms-vsliveshare.vsliveshare /tmp/d2b8043d-198c-472e-9393-1ba48b2e4894 [2020-04-01 16:13:09.614] [remoteagent] [info] Extracted extension to /home/net/b/brt24574/.vscode-server/extensions/.ms-vsliveshare.vsliveshare-1.0.1847: ms-vsliveshare.vsliveshare [2020-04-01 16:13:09.615] [remoteagent] [info] Renamed to /home/.vscode-server/extensions/ms-vsliveshare.vsliveshare-1.0.1847 [2020-04-01 16:13:09.621] [remoteagent] [info] Installation completed. ms-vsliveshare.vsliveshare [2020-04-01 16:13:09.652] [remoteagent] [info] Extensions installed successfully: ms-vsliveshare.vsliveshare [2020-04-01 16:13:23.566] [remoteagent] [info] [127.0.0.1][50f785bc][ManagementConnection] The client has disconnected gracefully, so the connection will be disposed.

Installed multiple versions of the extensions multiple times without luck.

No matter the version of Live Share installed, the same dotnet-3.1.1 remained and no others were added.

I've also installed VS Code on my Linux server, connected my computer to the server over ssh with the -Y switch from terminal to run a remote X window using XQuartz. I cd into the project folder and issue command 'code .'
I was unable get past the "corrupted download"

My Setup
Mac Catalina 10.15.3
VS CODE Version: 1.43.2
Commit: 0ba0ca52957102ca3527cf479571617f0de6ed50
Date: 2020-03-24T07:34:57.037Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.3.0

brt24574 on 2 Apr 2020

Encountering this issue as well. Re-installing does not seem to fix the problem.

MacOS Mojave 10.14.6

Content of ~/.vscode/extensions:

JerryHong.autofilename-0.1.3                       johnpapa.vscode-peacock-3.6.0                      qinjia.seti-icons-0.1.3
Tyriar.lorem-ipsum-1.2.0                           mechatroner.rainbow-csv-1.6.0                      shan.code-settings-sync-3.4.3
alefragnani.bookmarks-11.0.0                       medienbaecker.kirby-snippets-3.0.2                 shanoor.vscode-nginx-0.6.0
bmewburn.vscode-intelephense-client-1.3.11         mikestead.dotenv-1.0.1                             streetsidesoftware.code-spell-checker-1.8.0
bungcip.better-toml-0.3.2                          mrmlnc.vscode-apache-1.2.0                         streetsidesoftware.code-spell-checker-french-0.1.6
coenraads.bracket-pair-colorizer-2-0.0.29          ms-azuretools.vscode-docker-1.0.0                  vscode-icons-team.vscode-icons-10.0.0
cssho.vscode-svgviewer-2.0.0                       ms-python.python-2018.10.1                         waderyan.gitblame-3.2.0
darkriszty.markdown-table-prettify-2.4.0           neilding.language-liquid-0.1.1                     wayou.vscode-todo-highlight-1.0.4
dracula-theme.theme-dracula-2.21.0                 octref.vetur-0.14.2                                whatwedo.twig-1.0.2
editorconfig.editorconfig-0.14.4                   octref.vetur-0.24.0                                wix.vscode-import-cost-2.11.1
esbenp.prettier-vscode-3.20.0                      onecentlin.laravel-blade-1.20.0                    yzhang.markdown-all-in-one-2.7.0
felixfbecker.php-pack-1.0.2                        phproberto.vscode-php-getters-setters-1.2.3

fbnlsr on 3 Apr 2020

Hello everyone,

After getting this link that is saying that my install is corrupted. I tried to reinstall it.

After reinstall I got this error in Extension Host:

System: OS-X

[2020-04-02 11:39:13.014] [exthost] [info] ExtensionService#loadCommonJSModule file:///Users/valeriialigorskii/.vscode/extensions/ms-vsliveshare.vsliveshare-1.0.1891/out/prod/extension-prod
[2020-04-02 11:39:16.122] [exthost] [error] Activating extension ms-vsliveshare.vsliveshare failed due to an error:
[2020-04-02 11:39:16.122] [exthost] [error] Error: Agent terminated with exit code: 0 and signal null: Error:
  An assembly specified in the application dependencies manifest (Microsoft.NETCore.App.deps.json) was not found:
    package: 'runtime.win-x86.Microsoft.NETCore.App', version: '3.1.1-servicing.19608.4'
    path: 'runtimes/win-x86/native/API-MS-Win-core-xstate-l2-1-0.dll'
  at ChildProcess.<anonymous> (/Users/valeriialigorskii/.vscode/extensions/ms-vsliveshare.vsliveshare-1.0.1891/out/prod/extension-prod.js:138672:32)
  at ChildProcess.emit (events.js:208:15)
  at maybeClose (internal/child_process.js:1021:16)
  at Socket.<anonymous> (internal/child_process.js:430:11)
  at Socket.emit (events.js:203:13)
  at Pipe.<anonymous> (net.js:588:12)

I also installed .NET Core to Mac OS X, but it didn't help

Version: 1.43.2
Commit: 0ba0ca52957102ca3527cf479571617f0de6ed50
Date: 2020-03-24T07:34:57.037Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.3.0

RyuuGan on 3 Apr 2020

The directory in the error message did not exist as far as I could tell.
…
On Mar 30, 2020, at 2:45 PM, Luke Wolf @.*> wrote: @jeremygaither Try going to that directory and deleting the folder by right clicking on it and clicking "delete". — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

C:\Users\USER_NAME\AppData\Roaming\Code\UserglobalStoragems-vsliveshare.vsliveshare

It should exist.
Change the USER_NAME part of the directory to the name of your desktop user account.
If you're not sure what that is, go to C:\Users\ and you should see a folder with the name of your desktop user account.

After that if it still does not exist you can try going to .vscode inside C:\Users\, go into the extentions folder and delete the ms-vsliveshare.vsliveshare folder.

Then inside vs code: this should force it to not recognise that the extension is installed and indicate that you can install it inside the extensions tab, then if you continue getting that error, you should be able to find the dotnet-3.1.1 folder that you could not find at all.

If that does not work, prepare to uninstall vscode itself before re-downloading the latest version and installing it again as well as the extension, then try to look for that dotnet folder again to delete it manually.

LukeWolfGames on 3 Apr 2020

@LukeWolfGames The problem that it is in Mac OS X, I it might be not working that API-MS-Win-core-xstate-l2-1-0.dll should not be included to Mac OS X extension.

RyuuGan on 3 Apr 2020

Cross posting to #180 and #3252.

We have a hacky simple workaround for our particular case.

Can confirm that this is an issue for the limited case of doing Live Share with Remote Development (ssh) on a shared remote machine (the shared compute cluster on our campus). Our use case is remote learning for our students.

We (myself plus @peterbatzel and @Leslie-C) have been banging our heads against this for over a day. The original error is this:

That link (https://aka.ms/vsls-corrupted-install) is just a redirect to #180, which is two years old with maybe hundreds of comments. It looks like there are possibly multiple causes of that error message in #180 that are unrelated to the remote ssh problem we're experiencing (the word "remote" doesn't get mentioned in #180 until Jul 31, 2019).

Everything worked for me (I was the first to install it), but it was corrupt corrupt corrupt for my colleagues @peterbatzel and then @Leslie-C. @peterbatzel then found #3252, and just as @bjorngadde describes it, I (@jasonsydes) had ownership of the /tmp/VSFeedbackVSRTCLogs directory, and @peterbatzel and @Leslie-C couldn't write to it when they tried to install Live Share there.

Our simple hacky solution is to just have the original owner (me in this case) open up permissions to allow everyone to write to that directory:

chmod a+w /tmp/VSFeedbackVSRTCLogs

Again, that directory is not on our laptops, but rather is located on our university's shared compute cluster. Once I ran that command, @Leslie-C was able to install Live Share just fine (no more "corruption", or rather, she was able to write to the directory, see below) and we were able to do a Live Share session together on the compute cluster.

Obviously not a perfect solution (security implications?), would prefer a different fix (e.g. write to ~/.vscode-server/ instead), but works for now.

Thanks VSCode community!

jasonsydes on 9 Apr 2020

🚀2 👍2

@jamescasbon, @pkeogan, @deinhofer, @andremacola, @geoffrey4444, @aracpyon, @jonator, @bmfisher and @brt24574 (just grabbing everyone who used the word "remote" in this thread), it's possible that my previous post addresses the problem you were having with a "corrupt" download of Live Share in a Remote (SSH) environment? Look right above, or here's the link:
https://github.com/MicrosoftDocs/live-share/issues/180#issuecomment-611228433

jasonsydes on 9 Apr 2020

❤1

Thanks for helping with this @jasonsydes . I just checked our permissions and confirmed that they belong to @jator who is the only one on our university server that can currently run Live Share. I bet once he changes them I will also gain access.

bmfisher on 9 Apr 2020

👍1

The Live Share team appreciates the collaborative discussion in this thread.

We learned a lot from your pain, and I am glad to announce our latest release 1.0.1947 automates the fix of corrupted installs. Other than permission issues that we can't fix, we hope updating to this version helps all of you hitting an install problem.

BrunoGuardia on 9 Apr 2020

🎉1

@jasonsydes We were having the exact same experience. Once files in /tmp were cleared, we were able to strong arm the use of live share from another team by starting a session first, presumably preventing that team from using it again. Hopefully 1.0.1947 includes fixes for this.

jonator on 9 Apr 2020

@BrunoGuardia thanks a lot for your work. Unfortunately, no luck for me. I had the extension uninstalled, and re-installed it after seeing your comment. I still get the "corrupted download" notification.

fbnlsr on 9 Apr 2020

@BrunoGuardia, thank you for your attention to this. I don't know if your 1.0.1947 fixes other causes of the error listed in this thread, but w/r/t to the "Remote - SSH" + "Live Share" error described in #3252, without write permission to the shared directory /tmp/VSFeedbackVSRTCLogs/, I'm still seeing the corrupted download error (see below) when trying to install version 1.0.1947 of "Live Share" with "Remote - SSH". (This means that only one user out of thousands on a shared compute cluster will be able to use Live Share, which seems to defeat the purpose of Live Share.)

Would moving the logs to somewhere unique for each user be possible? If so, that would seem to be one solution to this problem. Maybe something like /tmp/VSFeedbackVSRTCLogs-$USER (e.g. for me, my username is "sydes", so for me it would be /tmp/VSFeedbackVSRTCLogs-sydes/). Or, as others have suggested, somewhere in /home/$USER/.vscode-server/ ?

This should not be considered a "permission issues that we can't fix" as you say, but a "where should we store the logs issue" that you can fix.

Thank you!!

jasonsydes on 9 Apr 2020

We are looking at what else we can fix, like the unique user you suggest. Storing the logs on /home instead of /tmp would have further implications that may not be desirable.

@fbnlsr - can you provide logs for us to check?

BrunoGuardia on 9 Apr 2020

@fbnlsr For the record, I initially sleuthed this out by hitting that "corrupted download" error, and then from the same window the error message was displayed, opening up the Command Palette -> Developer: Show Logs... -> Remote Extension Host. That may get you to the relevant logs that @BrunoGuardia is asking for.

peterbatzel on 9 Apr 2020

Could this be related to settings-sync extension? I did not run into this issue until syncing my settings with it.

joech4n on 9 Apr 2020

@peterbatzel thanks for the tip ! 😄

@BrunoGuardia here is my extension host log, I hope it'll help you: https://gist.github.com/fbnlsr/9e6c8c40a0bb878d3da779259697b2c1

fbnlsr on 10 Apr 2020

@joech4n Seems like I have a similar issue. I do have the same settings-sync extension.

JamesTeague on 11 Apr 2020

uld this be related to settings-sync extension? I did not run into this issue until syncing my settings with it.

I'll add to the list of people that also have settings sync addon. However I've used this addon along side live share for a long time so would be a recent update if related at all.

wade-montague on 14 Apr 2020

@BrunoGuardia If you make a random directory in /tmp with 'mktemp' or similar, this might sort of work. But trying to camp on a specific file/directory in /tmp will never work reliably.

Alternatively, short of a real fix, could you get your software to simply ignore all errors when trying to write to this camped directory?

michaelkarlcoleman on 15 Apr 2020

👍1

@LukeWolfGames i think i've find the folder on windows: C:\Users\USER_NAME\AppData\Roaming\Code\User\globalStorage\ms-vsliveshare.vsliveshare
There you have to delete the dotnet-3.1.1 folder.
USER_NAME is your user folder.

Finally, after have tried every solution listed here, this is your solution that solved my problem.

To help others, this is all the steps I did on Windows :

Uninstall "Live share" from VSCode, then close the editor.
Open an explorer and navigate to: %USERPROFILE%/.vscode/extensions
Remove manually every folder that match ms-vsliveshare.vsliveshare-*.*.****
Still in the explorer, navigate to %AppData%/Code/User/globalStorage/ms-vsliveshare.vsliveshare
Remove the dotnet-3.1.1 folder.
Open VSCode and reinstall "Live Share" in the normal way
Enjoy! 🎉

Thank you @MJECloud !

My system setup :

Version : 1.44.2 (system setup)
Validation : ff915844119ce9485abfe8aa9076ec76b5300ddd
Date : 2020-04-16T16:36:23.138Z
Électron : 7.1.11
Chrome : 78.0.3904.130
Node.js : 12.8.1
V8 : 7.8.279.23-electron.0
OS : Windows_NT x64 10.0.18362

jmpp on 18 Apr 2020

👍5 ❤2 🎉2

uld this be related to settings-sync extension? I did not run into this issue until syncing my settings with it.

I'll add to the list of people that also have settings sync addon. However I've used this addon along side live share for a long time so would be a recent update if related at all.

I originally thought that this could be the case but when I set it up in a Windows environment, it seemed to install just fine. I had issues when on Ubuntu.

JamesTeague on 19 Apr 2020

Reinstalling doesn't fix my issue, it always gives corrupt error. The latest version I have successfully installed is 1.0.1510 and on that version I've only been able to host, but not join a session.

cholman on 21 Apr 2020

Ran into this problem today on my Pinebook Pro with the Headmelted build:

nelson@annalise /e/ansible> code-oss --version
1.45.0
6526fe0a1ade9d8f6e566811f4118191b84bf9f7
arm64

What I have installed is:

nelson@annalise /e/ansible> ls ~/.vscode-oss/extensions/
bmalehorn.vscode-fish-1.0.14/  bungcip.better-toml-0.3.2/            tommasov.hosts-1.1.1/         wholroyd.jinja-0.0.8/
bmalehorn.vscode-fish-1.0.16/  ms-vsliveshare.vsliveshare-1.0.2000/  vscoss.vscode-ansible-0.5.2/

Uninstalling and reinstalling did nothing.

skyfaller on 22 Apr 2020

I was hit by this today and re-installing live share does not help.

Full log:

[2020-04-23 09:41:44.357] [exthost] [info] extension host started
[2020-04-23 09:41:44.408] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch {"startup":true,"extensionId":{"value":"vscode.debug-auto-launch","_lower":"vscode.debug-auto-launch"},"activationEvent":"*"}
[2020-04-23 09:41:44.409] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/eavefre/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/debug-auto-launch/dist/extension
[2020-04-23 09:41:44.414] [exthost] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"extensionId":{"value":"vscode.emmet","_lower":"vscode.emmet"},"activationEvent":"*"}
[2020-04-23 09:41:44.415] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/eavefre/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/emmet/dist/extension
[2020-04-23 09:41:44.439] [exthost] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"extensionId":{"value":"vscode.git","_lower":"vscode.git"},"activationEvent":"*"}
[2020-04-23 09:41:44.439] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/eavefre/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/git/dist/main
[2020-04-23 09:41:44.457] [exthost] [info] ExtensionService#_doActivateExtension vscode.github-authentication {"startup":true,"extensionId":{"value":"vscode.github-authentication","_lower":"vscode.github-authentication"},"activationEvent":"*"}
[2020-04-23 09:41:44.457] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/eavefre/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/github-authentication/dist/extension.js
[2020-04-23 09:41:44.463] [exthost] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"extensionId":{"value":"vscode.merge-conflict","_lower":"vscode.merge-conflict"},"activationEvent":"*"}
[2020-04-23 09:41:44.464] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/eavefre/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/merge-conflict/dist/extension
[2020-04-23 09:41:44.468] [exthost] [info] ExtensionService#_doActivateExtension vscode.search-result {"startup":true,"extensionId":{"value":"vscode.search-result","_lower":"vscode.search-result"},"activationEvent":"*"}
[2020-04-23 09:41:44.468] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/eavefre/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/search-result/dist/extension.js
[2020-04-23 09:41:44.469] [exthost] [info] ExtensionService#_doActivateExtension vscode.vscode-account {"startup":true,"extensionId":{"value":"vscode.vscode-account","_lower":"vscode.vscode-account"},"activationEvent":"*"}
[2020-04-23 09:41:44.470] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/eavefre/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/vscode-account/dist/extension.js
[2020-04-23 09:41:44.476] [exthost] [info] ExtensionService#_doActivateExtension alefragnani.project-manager {"startup":true,"extensionId":{"value":"alefragnani.project-manager","_lower":"alefragnani.project-manager"},"activationEvent":"*"}
[2020-04-23 09:41:44.476] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/eavefre/.vscode/extensions/alefragnani.project-manager-10.11.0/dist/extension
[2020-04-23 09:41:44.481] [exthost] [info] ExtensionService#_doActivateExtension johnpapa.vscode-peacock {"startup":true,"extensionId":{"value":"johnpapa.vscode-peacock","_lower":"johnpapa.vscode-peacock"},"activationEvent":"*"}
[2020-04-23 09:41:44.481] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/eavefre/.vscode/extensions/johnpapa.vscode-peacock-3.7.0/dist/extension
[2020-04-23 09:41:44.487] [exthost] [info] ExtensionService#_doActivateExtension ms-vsliveshare.vsliveshare {"startup":true,"extensionId":{"value":"ms-vsliveshare.vsliveshare","_lower":"ms-vsliveshare.vsliveshare"},"activationEvent":"*"}
[2020-04-23 09:41:44.487] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/eavefre/.vscode/extensions/ms-vsliveshare.vsliveshare-1.0.2048/out/prod/extension-prod
[2020-04-23 09:41:44.709] [exthost] [info] ExtensionService#_doActivateExtension Shan.code-settings-sync {"startup":true,"extensionId":{"value":"Shan.code-settings-sync","_lower":"shan.code-settings-sync"},"activationEvent":"*"}
[2020-04-23 09:41:44.710] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/eavefre/.vscode/extensions/shan.code-settings-sync-3.4.3/out/extension.js
[2020-04-23 09:41:45.174] [exthost] [info] ExtensionService#_doActivateExtension shardulm94.trailing-spaces {"startup":true,"extensionId":{"value":"shardulm94.trailing-spaces","_lower":"shardulm94.trailing-spaces"},"activationEvent":"*"}
[2020-04-23 09:41:45.174] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/eavefre/.vscode/extensions/shardulm94.trailing-spaces-0.3.1/out/src/extension
[2020-04-23 09:41:45.214] [exthost] [info] ExtensionService#_doActivateExtension yzhang.markdown-all-in-one {"startup":true,"extensionId":{"value":"yzhang.markdown-all-in-one","_lower":"yzhang.markdown-all-in-one"},"activationEvent":"workspaceContains:README.md"}
[2020-04-23 09:41:45.214] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/eavefre/.vscode/extensions/yzhang.markdown-all-in-one-2.8.0/dist/extension
[2020-04-23 09:41:45.348] [exthost] [info] eager extensions activated
[2020-04-23 09:41:47.443] [exthost] [error] Activating extension ms-vsliveshare.vsliveshare failed due to an error:
[2020-04-23 09:41:47.443] [exthost] [error] Error: Agent terminated with exit code: 0 and signal null: Error:
  Anassembly specified in the application dependencies manifest (Microsoft.NETCore.App.deps.json) was not found:
    package: 'runtime.linux-x64.Microsoft.NETCore.App', version: '3.1.1-servicing.19608.4'
    path: 'runtimes/linux-x64/native/System.Globalization.Native.so'
    at ChildProcess.<anonymous> (c:\Users\eavefre\.vscode\extensions\ms-vsliveshare.vsliveshare-1.0.2048\out\prod\extension-prod.js:140937:32)
    at ChildProcess.emit (events.js:208:15)
    at maybeClose (internal/child_process.js:1021:16)
    at Socket.<anonymous> (internal/child_process.js:430:11)
    at Socket.emit (events.js:203:13)
    at Pipe.<anonymous> (net.js:588:12)
[2020-04-23 09:41:47.443] [exthost] [error] Activating extension johnpapa.vscode-peacock failed due to an error:
[2020-04-23 09:41:47.443] [exthost] [error] Error: Agent terminated with exit code: 0 and signal null: Error:
  Anassembly specified in the application dependencies manifest (Microsoft.NETCore.App.deps.json) was not found:
    package: 'runtime.linux-x64.Microsoft.NETCore.App', version: '3.1.1-servicing.19608.4'
    path: 'runtimes/linux-x64/native/System.Globalization.Native.so'
    at ChildProcess.<anonymous> (c:\Users\eavefre\.vscode\extensions\ms-vsliveshare.vsliveshare-1.0.2048\out\prod\extension-prod.js:140937:32)
    at ChildProcess.emit (events.js:208:15)
    at maybeClose (internal/child_process.js:1021:16)
    at Socket.<anonymous> (internal/child_process.js:430:11)
    at Socket.emit (events.js:203:13)
    at Pipe.<anonymous> (net.js:588:12)

Version: 1.44.2 (user setup)
Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd
Date: 2020-04-16T16:36:23.138Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.17763

fredrikaverpil on 23 Apr 2020

I use Linux Mint, with two different users that share vscode installation, but with separated configs and extensions.
One user have live share extension installed and working. This was the first installation of live share in this machine.
When I tried to install live share on the other user I faced with this corruption error.
It was still working on the previous user though.

Tried all the suggested fixes above (deleting folders, install previous version, reinstall, etc) but without success.

I opened the dev tool to check the console while installing live share. It showed this error:

It was trying to access a log file, but it didn't have permission.
/tmp/VSFeedbackVSRLCLogs/20200424_140442_Agent.log

I simply gave read and write permission to the current user to the /tmp/VSFeedbackVSRLCLogs folder and the installation finally worked.

Uirado on 24 Apr 2020

👍1

@LukeWolfGames i think i've find the folder on windows: C:\Users\USER_NAME\AppData\Roaming\Code\User\globalStorage\ms-vsliveshare.vsliveshare
There you have to delete the dotnet-3.1.1 folder.
USER_NAME is your user folder.

Finally, after have tried every solution listed here, this is your solution that solved my problem.

To help others, this is all the steps I did on Windows :

Uninstall "Live share" from VSCode, then close the editor.

Open an explorer and navigate to: %USERPROFILE%/.vscode/extensions

Remove manually every folder that match ms-vsliveshare.vsliveshare-*.*.****

Still in the explorer, navigate to %AppData%/Code/User/globalStorage/ms-vsliveshare.vsliveshare

Remove the dotnet-3.1.1 folder.

Open VSCode and reinstall "Live Share" in the normal way

Enjoy! tada

Step 4 is what finally worked for me in Linux. You'll find those folders under ~/.config/Code/User/globalStorage. After uninstalling the extensions, removing the folders under .vscode/extensions, I simply deleted the two folders in that globalStorage folder and re-installed the extensions. Seems fine now. Thanks!

kevin-guertin on 26 Apr 2020

🎉1

@LukeWolfGames i think i've find the folder on windows: C:\Users\USER_NAME\AppData\Roaming\Code\User\globalStorage\ms-vsliveshare.vsliveshare
There you have to delete the dotnet-3.1.1 folder.
USER_NAME is your user folder.

Finally, after have tried every solution listed here, this is your solution that solved my problem.
To help others, this is all the steps I did on Windows :

Uninstall "Live share" from VSCode, then close the editor.

Open an explorer and navigate to: %USERPROFILE%/.vscode/extensions

Remove manually every folder that match ms-vsliveshare.vsliveshare-*.*.****

Still in the explorer, navigate to %AppData%/Code/User/globalStorage/ms-vsliveshare.vsliveshare

Remove the dotnet-3.1.1 folder.

Open VSCode and reinstall "Live Share" in the normal way

Enjoy! tada

Step 4 is what finally worked for me in Linux. You'll find those folders under ~/.config/Code/User/globalStorage. After uninstalling the extensions, removing the folders under .vscode/extensions, I simply deleted the two folders in that globalStorage folder and re-installed the extensions. Seems fine now. Thanks!

As a Mac user, steps 3, 4 and 5 were key. The 'AppData' equivalent for macOS Catalina is:

/Users/\

And the equivalent path of step 2 is a hidden folder under

/Users/\

To see hidden folders, press cmd + shift + . (the 'dot' key).

nikensss on 26 Apr 2020

🚀2

@avanderhoorn What if my issue is with Visual Studio and I haven't been able to update the extension in a couple weeks? And I can't uninstall it, only disable or revert it which reverting also fails, not sure what it does. Here's the log file when updating fails.

dd_VSIXInstaller_20200427191820_0694.log

DanJ210 on 28 Apr 2020

Hey @DanJ210 , it looks like something in your Visual Studio setup must be broken (the error in that log is due to trying to parse invalid JSON it looks like!) I'd recommend you go through Visual Studio repair steps. I suspect this would impact things besides just your Live Share install as well.

daytonellwanger on 28 Apr 2020

I've tried multiple versions etc, always the same error...

[2020-05-04 10:54:48.434] [exthost] [error] Error: Agent terminated with exit code: 0 and signal null: Error:
  An assembly specified in the application dependencies manifest (Microsoft.NETCore.App.deps.json) was not found:
    package: 'runtime.win-x86.Microsoft.NETCore.App', version: '3.1.1-servicing.19608.4'
    path: 'runtimes/win-x86/native/API-MS-Win-core-xstate-l2-1-0.dll'
    at ChildProcess.<anonymous> (~/.vscode/extensions/ms-vsliveshare.vsliveshare-1.0.2104/out/prod/extension-prod.js:141023:32)
    at ChildProcess.emit (events.js:208:15)
    at maybeClose (internal/child_process.js:1021:16)
    at Socket.<anonymous> (internal/child_process.js:430:11)
    at Socket.emit (events.js:203:13)
    at Pipe.<anonymous> (net.js:588:12)

@fredrikaverpil we have a similar issue, did you find a solution?

I'll edit this if I can make it work again

edit

I removed all dotnet runtimes and sdk's and reinstalled them with no positive outcome.

Installing vscode insiders was the only solution that works right now.

steveoh on 4 May 2020

@steveoh - can you confirm which is the most recent LiveShare version you have tried with? There is a new command "Live Share Repair Installation", available from the Command Palette. Please update if this doesn't get your issue solved.

BrunoGuardia on 4 May 2020

👀1

@steveoh - can you confirm which is the most recent LiveShare version you have tried with? There is a new command "Live Share Repair Installation", available from the Command Palette. Please update if this doesn't get your issue solved.

I am on 1.0.2104 and there is no repair command pallet entry and no option to update to a newer version

steveoh on 4 May 2020

@LukeWolfGames i think i've find the folder on windows: C:\Users\USER_NAME\AppData\Roaming\Code\User\globalStorage\ms-vsliveshare.vsliveshare
There you have to delete the dotnet-3.1.1 folder.
USER_NAME is your user folder.

Finally, after have tried every solution listed here, this is your solution that solved my problem.
To help others, this is all the steps I did on Windows :

Uninstall "Live share" from VSCode, then close the editor.

Open an explorer and navigate to: %USERPROFILE%/.vscode/extensions

Remove manually every folder that match ms-vsliveshare.vsliveshare-*.*.****

Still in the explorer, navigate to %AppData%/Code/User/globalStorage/ms-vsliveshare.vsliveshare

Remove the dotnet-3.1.1 folder.

Open VSCode and reinstall "Live Share" in the normal way

Enjoy! tada

Step 4 is what finally worked for me in Linux. You'll find those folders under ~/.config/Code/User/globalStorage. After uninstalling the extensions, removing the folders under .vscode/extensions, I simply deleted the two folders in that globalStorage folder and re-installed the extensions. Seems fine now. Thanks!

If you have installed live-share on a linux remote system with remote-ssh (yes live-share works also on a remote workspace :D) you will find the folders under

rm -r ~/.vscode-server/extensions/ms-vsliveshare*
rm -r ~/.vscode-server/data/User/globalStorage/ms-vsliveshare.vsliveshare

JumpLink on 7 May 2020

👍4

@LukeWolfGames i think i've find the folder on windows: C:\Users\USER_NAME\AppData\Roaming\Code\User\globalStorage\ms-vsliveshare.vsliveshare
There you have to delete the dotnet-3.1.1 folder.
USER_NAME is your user folder.

Finally, after have tried every solution listed here, this is your solution that solved my problem.
To help others, this is all the steps I did on Windows :

Uninstall "Live share" from VSCode, then close the editor.

Open an explorer and navigate to: %USERPROFILE%/.vscode/extensions

Remove manually every folder that match ms-vsliveshare.vsliveshare-*.*.****

Still in the explorer, navigate to %AppData%/Code/User/globalStorage/ms-vsliveshare.vsliveshare

Remove the dotnet-3.1.1 folder.

Open VSCode and reinstall "Live Share" in the normal way

Enjoy! tada

Step 4 is what finally worked for me in Linux. You'll find those folders under ~/.config/Code/User/globalStorage. After uninstalling the extensions, removing the folders under .vscode/extensions, I simply deleted the two folders in that globalStorage folder and re-installed the extensions. Seems fine now. Thanks!

If you have installed live-share on a linux remote system with remote-ssh (yes live-share works also on a remote workspace :D) you will find the folders under
rm -r ~/.vscode-server/extensions/ms-vsliveshare*
rm -r ~/.vscode-server/data/User/globalStorage/ms-vsliveshare.vsliveshare

This did it for me, thanks!

Hibbins on 12 May 2020

I use Linux Mint, with two different users that share vscode installation, but with separated configs and extensions.
One user have live share extension installed and working. This was the first installation of live share in this machine.
When I tried to install live share on the other user I faced with this corruption error.
It was still working on the previous user though.

Tried all the suggested fixes above (deleting folders, install previous version, reinstall, etc) but without success.

I opened the dev tool to check the console while installing live share. It showed this error:

It was trying to access a log file, but it didn't have permission.
/tmp/VSFeedbackVSRLCLogs/20200424_140442_Agent.log

I simply gave read and write permission to the current user to the /tmp/VSFeedbackVSRLCLogs folder and the installation finally worked.

I confirm that this is the reason for my corrupted install. Giving write access to the folder let has allow live share to install succcessfully. I feel that moving the log out of here to a user folder is a must. Otherwise, only 1 person could install it on a shared server

EricChen1248 on 14 May 2020

👍3

MacOS Catalina: 10.15.4 (19E287)
Live Share: Version 1.0.2169

I also am having this issue. It was working fine this morning then suddenly stopped working. No extensions updated during this time, it just stopped working and when I reloaded VS Code the message started showing up.

I have tried the following and none have worked:

Uninstalled Extension & Reinstall
Uninstalled Extension & deleted ~/.vscode/extensions/ms-vsliveshare.vsliveshare-1.0.2169 (did not work) & Reinstalled
Uninstalled and deleted everything/emptied the trash, I could with vsliveshare on my system & Reinstall
Tried @MJECloud solution in this thread.
Gave full permission on folder /System/Volumes/Data/private/var/folders/dp/fsg_vz7j7gjflb6x1jj7h3vr0000gn/T/VSFeedbackVSRTCLogs

webdevnerdstuff on 18 May 2020

👍1

macOS Mojave v 10.14.6
Live Share: Version 1.0.2169

Having issues where live share extension does not show up at all upon first installation and usage of it.

Cannot export logs

command 'liveshare.exportLogs' not found

I did try quitting and reinstalling Live Extension after removing it from the /%USERS/.vsc/extensions but same error as well.

YY-Huang on 20 May 2020

Ubuntu 20.04
Live Share: Version 1.0.2169
VS Code:
Version: 1.45.1
Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
Date: 2020-05-14T08:27:22.494Z
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 5.4.0-31-generic snap

After installing dotnet-sdk-3.1 via apt, the extension stopped working.
Uninstalling dotnet-sdk-3.1, unintsalling the extension, removing the folder ~/.config/Code/User/globalStorage/ms-vsliveshare.vsliveshare/dotnet-3.1.1/and rebooting the computer, and then re-installing the extension fixed the issue for me

mattschlosser on 21 May 2020

After installing dotnet-sdk-3.1 via apt, the extension stopped working.
Uninstalling dotnet-sdk-3.1, unintsalling the extension, removing the folder ~/.config/Code/User/globalStorage/ms-vsliveshare.vsliveshare/dotnet-3.1.1/and rebooting the computer, and then re-installing the extension fixed the issue for me

come to think of it, i think a dotnet sdk install might have happened around the time of my corruption

steveoh on 21 May 2020

An update or installation of VS Live Share failed due to a corrupted download. Please uninstall and reinstall the extension to resolve. See https://aka.ms/vsls-corrupted-install for more details.

I uninstalled it from vs code and reinstalled it and it didn't work, and deleted from the vs code folder in my windows 10 laptop as well and didn't work

JoshuaKornmayer on 29 May 2020

@JoshuaKornmayer - Which versions of VSCode and LiveShare are you trying?

There is a new command "Live Share Repair Installation", available from the Command Palette. Can you try it and confirm the result?

BrunoGuardia on 29 May 2020

VS Code version 1.45.1 and live share version 1.0.2236

How do I get to the Live Share Repair Installation?

JoshuaKornmayer on 29 May 2020

I tried the live share repair installation and it still didn't fix the live share. STill has the same error measure

JoshuaKornmayer on 29 May 2020

Ctrl + Shift + P - brings the Command Palette. Then you can start typing Live Share : Repair Installation

BrunoGuardia on 29 May 2020

👍9 🎉2

Ok... Can you share your Live Share logs then? Seems we have some work to improve the repair.

Ctrl + Shift + P then Live Share : Export Logs

BrunoGuardia on 29 May 2020

liveshareVSCode.zip

JoshuaKornmayer on 29 May 2020

any updates on if/when this can be fixed?

JoshuaKornmayer on 1 Jun 2020

When I run into this issue, neither repair nor numerous reinstalls worked. In the end, giving write permission to the entire /tmp dir worked. This is @Uirado 's solution. For me, too, this situation arose with VSCode and multiple-users.

sjdv1982 on 8 Jun 2020

When I run into this issue, neither repair nor numerous reinstalls worked. In the end, giving write permission to the entire /tmp dir worked. This is @Uirado 's solution. For me, too, this situation arose with VSCode and multiple-users.

me too on debian env with multiple users
sudo chmod +rw /tmp/VSFeedbackVSRTCLogs

tomyjwu on 11 Jun 2020

👍1

I have run into this issue today. I've tried uninstalling and reinstalling twice and still get the error message.

I have version 1.0.2302 installed.

spencerudnick on 15 Jun 2020

@spencerudnick - Did you try the Live Share / Repair Installation command?

BrunoGuardia on 15 Jun 2020

👍1

Is Live Share part of the ms-vscode-remote.remote-ssh-0.51.0 extension ?
I only have these in my entension folder and stil get that error :

ms-vscode-remote.remote-ssh-0.51.0
ms-vscode-remote.remote-ssh-edit-0.51.0

daslicht on 18 Jun 2020

Is Live Share part of the ms-vscode-remote.remote-ssh-0.51.0 extension ?
I only have these in my entension folder and stil get that error :

ms-vscode-remote.remote-ssh-0.51.0
ms-vscode-remote.remote-ssh-edit-0.51.0

Remote SSH is not part of Live Share, these are two different extensions for different tasks:

With Live Share you can share your workspace with other developers for collaborative editing as you know it e.g. from Google Docs, but for your source code.
With Remote SSH you can have a workspace on a remote machine like a server on which your project runs without the need to mount the filesystem from the server on your local machine (which would also be much slower).

If you use Remote SSH you can also install any VSCode extensions, if you do this the extensions will not be installed on your local VSCode instance, the extensions will be installed on the server. Your local VSCode instance will then load the extensions from the server. This way everyone has the same extensions who connects to the server via remote ssh.

You can also combine Remote SSH and Live Share, in this case Live Share is installed on the server. It worked for me but it is not as stable as the normal local installation, maybe that's why you came to this issue, I also got an error message this way with a link to this issue ;)

Live Share on a remote machine still works for me (but no audio and no chat), so if you don't need chat and audio you can probably ignore the error message from VSCode, or not?

Has anyone else experience with this setup?

JumpLink on 19 Jun 2020

👍1

@JumpLink Thank you very much for the detailed answer ! <3

daslicht on 19 Jun 2020

@JumpLink - thanks for sharing the context on Remote SSH. Feel free to add your concerns with "not as stable as local installation" in other issues; in particular, we have a good understanding of #3252

Also, Chat should work now for your scenario (we deprecated the separate extension); will forward your feedback about audio limitations for remote machines.

BrunoGuardia on 19 Jun 2020

Having the same issue, seems to be related to .NET Core somehow?

[2020-06-21 20:47:00.793 Client I] Passed version check for Linux: found 4.15.0-106-generic
[2020-06-21 20:47:00.950 Client.Rpc V] RPCClient.init retryCount:0 currentRetryInterval:0
[2020-06-21 20:47:00.951 Debug.Rpc.Host V] TrackDebugManager created
[2020-06-21 20:47:00.954 Client.Rpc V] Agent connection not completed: Error: connect ENOENT /tmp/CoreFxPipe_vscode.8600f791b8eb8b42ab19ebc2ff4c87c8; Retrying...
[2020-06-21 20:47:00.955 Client.Rpc V] RPCClient.init retryCount:1 currentRetryInterval:100
[2020-06-21 20:47:00.955 Client.Agent V] Agent lock on:</<redacted>/<redacted>.lock>
[2020-06-21 20:47:00.956 Client.Agent I] starting agent with pipe:vscode.8600f791b8eb8b42ab19ebc2ff4c87c8
[2020-06-21 20:47:00.956 Client.Agent I] signalR service -> uri:https://signlr-prod.core.vsengsaas.visualstudio.com/api/signalr/signalrhub
[2020-06-21 20:47:00.974 Client.Agent I] Agent terminated with exit code: 0 and signal null: Error:
  An assembly specified in the application dependencies manifest (Microsoft.NETCore.App.deps.json) was not found:
    package: 'runtime.osx-x64.Microsoft.NETCore.App', version: '3.1.1-servicing.19608.4'
    path: 'runtimes/osx-x64/native/System.Globalization.Native.dylib'
[2020-06-21 20:47:00.981 Client I] Moved package files.
[2020-06-21 20:47:01.018 Client.Agent V] Agent unlocked
[2020-06-21 20:47:01.221 Client I] hash mismatch: ../../../.config/Code/User/globalStorage/ms-vsliveshare.vsliveshare/dotnet-3.1.1/libhostfxr.so (null does not match bb17f12a80e91b669a013911ca3b029a99c40445fda999999b4d9a106b54433b in manifest)
[2020-06-21 20:47:01.842 Client I] Deactivating extension from background agent startup.
[2020-06-21 20:47:01.843 Client I] Hub connection is being enabled...
[2020-06-21 20:47:01.845 Client I] Client deactivation requested.

ShaharHD on 21 Jun 2020

I use Linux Mint, with two different users that share vscode installation, but with separated configs and extensions.
One user have live share extension installed and working. This was the first installation of live share in this machine.
When I tried to install live share on the other user I faced with this corruption error.
It was still working on the previous user though.
Tried all the suggested fixes above (deleting folders, install previous version, reinstall, etc) but without success.
I opened the dev tool to check the console while installing live share. It showed this error:

It was trying to access a log file, but it didn't have permission.
/tmp/VSFeedbackVSRLCLogs/20200424_140442_Agent.log
I simply gave read and write permission to the current user to the /tmp/VSFeedbackVSRLCLogs folder and the installation finally worked.

I confirm that this is the reason for my corrupted install. Giving write access to the folder let has allow live share to install succcessfully. I feel that moving the log out of here to a user folder is a must. Otherwise, only 1 person could install it on a shared server

On linux a reboot will clean up the /tmp dir and the problem will disappear for a while.

sig9 on 24 Jun 2020

I use Linux Mint, with two different users that share vscode installation, but with separated configs and extensions.
One user have live share extension installed and working. This was the first installation of live share in this machine.
When I tried to install live share on the other user I faced with this corruption error.
It was still working on the previous user though.
Tried all the suggested fixes above (deleting folders, install previous version, reinstall, etc) but without success.
I opened the dev tool to check the console while installing live share. It showed this error:

It was trying to access a log file, but it didn't have permission.
/tmp/VSFeedbackVSRLCLogs/20200424_140442_Agent.log
I simply gave read and write permission to the current user to the /tmp/VSFeedbackVSRLCLogs folder and the installation finally worked.

I confirm that this is the reason for my corrupted install. Giving write access to the folder let has allow live share to install succcessfully. I feel that moving the log out of here to a user folder is a must. Otherwise, only 1 person could install it on a shared server

On linux a reboot will clean up the /tmp dir and the problem will disappear for a while.

Problem is, as an SSH shared dev environment, the linux server is almost never turned off, and not everyone will have root access to change permissions for the tmp folder (they do in my team, but probably not for many others).

EricChen1248 on 29 Jun 2020

@spencerudnick - Did you try the Live Share / Repair Installation command?

This fixed the bug, thanks :)

spencerudnick on 27 Jul 2020

👍1

For me, the issue occurred after I reset my pc while keeping personal files. The repair installation command worked like a charm nonetheless.

arnabanimesh on 29 Oct 2020

Live-share: [VSCode] Corrupted install of the Live Share extension

112 is a specific example of this general class of problem.

Most helpful comment

All 148 comments

Error:

Steps to Reproduce:

3178, #180

It seems that Live Share works best sharing local files

edit

Related issues