-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LiveShare complains running outside application directory #2408
Comments
this is apparently fixed with a While the underlying issue is with Squirrel - this surfaces in the LiveShare extension. Squirrel/Squirrel.Mac#182 (comment) |
Yeahhh, I wish your solution worked for me but sadly, no :( |
Got this issue as well. only live-share complains, though it works anyway. |
That solved the issue for me. |
So I've tried the fix and thought it worked, but apparently this issue only occurs for me when launching VS Code via the command line with |
I also have this issue. It happens when I open from spotlight and from using Is there a fix in the works for this? For now I'm just disabling the plugin until I need it. |
Yes seem to be happening because of Catalina |
So, it turns out the app was never actually in write mode even after me taking it out and putting it back in. I figured that out by trying to update the app and it said I can't update it in read-only mode. I thought LiveShare was glitching because I assumed I had fixed it. But what actually worked was uninstalling, re-installing, and dragging into the application folder, then holding shift while opening it. Hopefully that works for y'all too 🤷🏽♂️ |
This is fixed for me with It was annoying as hell till then, because clicking don't share again didn't disable the extension. Is the second problem (disable notification) something that needs to be looked into? |
This issue is resolved. Thank you for reporting this issue. If you face problems with you current Live Share usage, please feel free to reopen this issue. |
Worked for me as well |
I had to open the application it after copying to another location. I think this happens if you don't open VSCode after extracting it. So it assumes that you didn't copy it to applications folder. |
Weird solution but works |
Np that it's closed. Just a FYI, I installed vscode with homebrew |
Issue Type: Bug
Although I've run the 'Visual Studio Code.app' from my /Applications folder on macOS -- the Live Share extension still shows the following:
Prior to this, I did run from ~/Downloads -- but I cleaned up and reinstalled. My cleanup included everything from ~/Library ~/.vscode, etc.
I see this with both Stable and Insiders release
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: