live-share icon indicating copy to clipboard operation
live-share copied to clipboard

[VSCode] Corrupted install of the Live Share extension

Open avanderhoorn opened this issue 7 years ago • 186 comments

There is currently a known issue with VS Code that can result in a state where the Live Share extension can be corrupted. The current fix is to uninstall the Live Share extension and reinstall it again. If this doesn't fix your issue please, let us know.

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%.vscode\extensions
  • Mac ~/.vscode/extensions
  • Linux ~/.vscode/extensions

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

avanderhoorn avatar Apr 05 '18 19:04 avanderhoorn

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 avatar Apr 05 '18 21:04 codycraven

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

avanderhoorn avatar Apr 12 '18 06:04 avanderhoorn

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 avatar Apr 17 '18 08:04 posva

@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 avatar Apr 18 '18 03:04 codycraven

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 avatar Apr 18 '18 20:04 Chuxel

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:

  1. 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 avatar Apr 19 '18 03:04 AkshayKalose

@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%.vscode\extensions Mac ~/.vscode/extensions Linux ~/.vscode/extensions

codycraven avatar Apr 19 '18 04:04 codycraven

@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 avatar Apr 20 '18 00:04 AkshayKalose

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 avatar Sep 17 '18 22:09 dullahan8

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

koredefashokun avatar Sep 29 '18 21:09 koredefashokun

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

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

avanderhoorn avatar Sep 29 '18 22:09 avanderhoorn

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 avatar Sep 29 '18 23:09 koredefashokun

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

avanderhoorn avatar Oct 01 '18 13:10 avanderhoorn

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

image

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 avatar Oct 01 '18 14:10 Fubinator

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 avatar Oct 02 '18 04:10 kitlith

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 avatar Oct 17 '18 16:10 BradStell

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:

  1. Uninstall the extension from the marketplace
  2. 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)
  3. 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)
  4. 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>.
  5. Reinstall VS Live Share from the marketplace and then reload VSCode, looking for the "Live Share" indicator in the bottom status bar.
  6. Rejoice. Open a beer. And some code.

Tbhesswebber avatar Feb 09 '19 01:02 Tbhesswebber

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: image

MathyFurret avatar Feb 14 '19 20:02 MathyFurret

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 avatar Feb 16 '19 02:02 frank-dspeed

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 avatar Feb 28 '19 13:02 rdourado

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

avanderhoorn avatar Mar 01 '19 18:03 avanderhoorn

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

  1. code --uninstall-extension ms-vsliveshare.vsliveshare-pack
  2. code --uninstall-extension ms-vsliveshare.vsliveshare-audio
  3. code --uninstall-extension ms-vsliveshare.vsliveshare
  4. Command Pallete >Developer: Reload Window
  5. Reinstall latest

AndresHurtadoRMT avatar May 10 '19 12:05 AndresHurtadoRMT

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 avatar Jul 31 '19 09:07 jamescasbon

ms-python.python-2019.6.24221

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

pkeogan avatar Aug 13 '19 04:08 pkeogan

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 avatar Nov 06 '19 14:11 deinhofer

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 avatar Nov 27 '19 20:11 DanJ210

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 à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 avatar Dec 11 '19 03:12 andremacola

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%.vscode\extensions:

.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 avatar Jan 13 '20 04:01 Sebbs128

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 avatar Jan 14 '20 13:01 geoffrey4444

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 avatar Jan 15 '20 18:01 aracpyon