-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Unable to open workspace on Desktop #6853
Comments
If you press cancel and then try again without quitting VS Code. It does not help? |
@akosyakov It fails too quickly, i'm not able to press Cancel 3sqTOHdHvL.mp4 |
@borisyordanov from messages it looks like a token is invalid. Could you try following:
We should work on better handling in such cases. It could be that you switched accounts on Gitpod for instance? Hope to prioritize some bug fixing for VS Code desktop in Q1. |
It wasn't very clear how to follow your instructions @akosyakov. Here's what I tried (I use Windows):
I also noticed that Windows Defender is flagging gitpod executables as Trojans. I excluded gitpod from the virus protection settings, but it still doesn't work. |
There should be credential manager on windows which store tokens. It is important that you remove gitpod token from there, and then stop the local companion processes they usually prefixed with |
@akosyakov I appreciate you trying to help, but I really need clearer instructions on what to do. Here are some clarifying questions:
What tokens are you referring to?
How?
How? |
@filiptronicek Could you help here please? I don't have windows machine unfortunately. |
I just booted up my Windows 11 PC and everything works fine (although I needed to do it twice because at first, I got a SSH tunnel not configured error). @borisyordanov as @akosyakov mentioned, could you please remove all Gitpod credentials from the system keychain? To get there, do the following:
After that, in the |
@filiptronicek Could you elaborate on how to find and kill processes with gitpod in name? :) |
Sure thing, it's easy as pie, just open Powershell, and execute this command: taskkill /FI "IMAGENAME eq gitpod*" /F And if you're a bit more skeptical about killing processes on your system, you can inspect the processes that would be killed by the command above by running: tasklist /fi "IMAGENAME eq gitpod*" You can also stop them one-by-one with Task manager if you fancy |
Thank you very much for the detailed instructions! I can confirm the issue is resolved, I'm able to open workspaces in VSCode Desktop |
@filiptronicek @akosyakov I wanted to follow up on this and explain my experience thus far. I basically have to repeat the helpful debugging steps you provided every time I open a workspace. It appears to be impossible to have more than one workspace configured. It's possible to open the same workspace multiple times, but it's not possible to open two different workspaces at the same time, or in succession. My colleagues are experiencing the same issue. If a workspace had previously been open and a different one is opened, this error is displayed. logs
|
Thanks for the patience as we worked to get this fixed @borisyordanov 🙏 We'll be updating the connection method from desktop to Gitpod as part of: Which hopefully should resolve this issue for good. Removing issue from inbox for now. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bug description
When I chose the

Open in VSCode
option in the browser workspace, it doesn't open the workspace on the desktop. It instead just loads infinitelySteps to reproduce
Open in VSCode
option in a browser workspaceWorkspace affected
No response
Expected behavior
My local VSCode opens the workspace
Example repository
No response
Anything else?
The text was updated successfully, but these errors were encountered: