live-share
live-share copied to clipboard
[VS Code] [Audio] Request startOrJoinCall failed unexpectedly without providing any details.
Error: Request startOrJoinCall failed unexpectedly without providing any details.
Steps to Reproduce: 1. 2.
Version Data | |
---|---|
extensionName | VSLS-Audio |
extensionVersion | 0.1.91 |
applicationName | VSCode |
applicationVersion | 1.52.1 |
platformName | Linux |
platformVersion | 5.4.0-58-generic |
Hi, if you are still facing this issue, please attach your logs by running the command Live Share: Export Logs. This could be caused by a corrupt install, so please try running the command Live Share: repair audio installation as well.
cc @jramsay
I'm also having problems with the Live Share Audio extension. Each time I try to start a call I get this error:
Live Share Audio failed to start due to a corrupted download. Ensure you have network connectivity then click
Repair
to restart VS Code and attempt recovery.
Clicking repair doesn't solve the problem. I've also tried uninstalling and reinstalling the extension, and restarting VS Code.
Here are my logs: logs.zip
I'm on a M1 MacBook Air with VS Code 1.54.1.
Any update to provide on this issue - thanks in advance.
Looking in the logs it is clear to me what is the error:
[2022-01-05 22:09:40.458 ExternalAppCallingService E] Electron not found: /Users/my_username/Library/Application Support/Code/User/globalStorage/ms-vsliveshare.vsliveshare-audio/electron-4.2.12/dist/Electron.app/Contents/MacOS/Electron
That folder /Users/my_username/Library/Application Support/Code/User/globalStorage/ms-vsliveshare.vsliveshare-audio
don't even exist, and it isn't created no matter how many times I press repair or uninstall and install the extension.
@rafaelfranca same here, same error message in my logs. I tried reinstalling all the live share extensions -- same error. Maybe this is an M1 bug? Also, looks like this happened a couple years ago #2792 and was closed due to inactivity.
Could this be a Windows 10 bug? I've tried everything suggested here and on other websites but still get the same error.
We're unable to prioritize fixes to this area as we re-evaluate our priorities and product direction. We understand that this maybe disappointing. We appreciate your input and comments on this issue till now. We will soon be sunsetting this feature and will work towards a better use experience for communication needs for Live Share users from the editor.