Skip to content
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

Closed
cicorias opened this issue Jun 25, 2019 · 14 comments
Closed

LiveShare complains running outside application directory #2408

cicorias opened this issue Jun 25, 2019 · 14 comments

Comments

@cicorias
Copy link
Member

cicorias commented Jun 25, 2019

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:

You are running VS Code outside the Applications folder, so we cannot install support for joining sessions using a browser link. You can still join sessions manually.

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

Extension version: 1.0.471
VS Code version: Code 1.35.1 (c7d83e57cd18f18026a8162d042843bda1bcf21f, 2019-06-12T14:29:22.216Z)
OS version: Darwin x64 18.6.0
System Info
Item Value
CPUs Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)
GPU Status 2d_canvas: enabled
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
Load (avg) 3, 2, 1
Memory (System) 32.00GB (18.92GB free)
Process Argv -psn_0_311372
Screen Reader no
VM 0%

image

image

@cicorias
Copy link
Member Author

cicorias commented Jun 25, 2019

this is apparently fixed with a cmd + c from ~/Applications of the .app file then cmd + option + v to Desktop -- then another cmd + opption + v back to the ~/Applications folder.

While the underlying issue is with Squirrel - this surfaces in the LiveShare extension.

Squirrel/Squirrel.Mac#182 (comment)
sparkle-project/Sparkle#1012

@Matthewjarredondo
Copy link

Yeahhh, I wish your solution worked for me but sadly, no :(

@asaphe
Copy link

asaphe commented Oct 22, 2019

Got this issue as well. only live-share complains, though it works anyway.
just annoying having that pop-up.

@janosh
Copy link

janosh commented Nov 30, 2019

this is apparently fixed with a cmd + c from ~/Applications of the .app file then cmd + option + v to Desktop -- then another cmd + opption + v back to the ~/Applications folder.

That solved the issue for me.

@JosephTLyons
Copy link

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 code . or code <filename>, but not when opening it via spotlight or clicking the app icon. Anyone else still experiencing this bug? I didn't notice this until I got to Catalina.

@tr1s
Copy link

tr1s commented Jan 6, 2020

I also have this issue. It happens when I open from spotlight and from using code .. When I click "Never Show Again", it still continuously shows up when I open VS code for the first time. Moving the app to desktop and back to applications does not work.

Is there a fix in the works for this? For now I'm just disabling the plugin until I need it.

@DouggyC
Copy link

DouggyC commented Jan 10, 2020

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 code . or code <filename>, but not when opening it via spotlight or clicking the app icon. Anyone else still experiencing this bug? I didn't notice this until I got to Catalina.

Yes seem to be happening because of Catalina

@tr1s
Copy link

tr1s commented Jan 10, 2020

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 🤷🏽‍♂️

@tgrrr
Copy link

tgrrr commented Jan 16, 2020

This is fixed for me with 1.0.1482, thanks!

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?

@fubaduba
Copy link
Contributor

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.
-Live Share team

@Christelle-Joseph
Copy link

this is apparently fixed with a cmd + c from ~/Applications of the .app file then cmd + option + v to Desktop -- then another cmd + opption + v back to the ~/Applications folder.

That solved the issue for me.

Worked for me as well

@lordlycastle
Copy link

this is apparently fixed with a cmd + c from ~/Applications of the .app file then cmd + option + v to Desktop -- then another cmd + opption + v back to the ~/Applications folder.

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.

@rubenstolk
Copy link

this is apparently fixed with a cmd + c from ~/Applications of the .app file then cmd + option + v to Desktop -- then another cmd + opption + v back to the ~/Applications folder.

While the underlying issue is with Squirrel - this surfaces in the LiveShare extension.

Squirrel/Squirrel.Mac#182 (comment)
sparkle-project/Sparkle#1012

Weird solution but works

@tgrrr
Copy link

tgrrr commented Jun 2, 2020

Np that it's closed. Just a FYI, I installed vscode with homebrew

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

13 participants