VSCode Desktop with Multiple Accounts not possible
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
Hi, I am working for different Clients and have different bitbucket accounts for them. thats I have to have different Gitpod Accounts. I have used one to work local in VSCode Desktop. Now i want to open a workspace in the other account in my local vscode or vscode insiders and can not connect
what can I do ?
Could not even solve this by creating a team and adding both users to it
[10/29/2021, 10:53:46 AM] open workspace window: vscode://gitpod.gitpod-desktop/workspace/riedelwebsite?%7B%22instanceId%22%3A%222c4b7a7d-efec-4123-ba81-11e6bfd9d15b%22%2C%22workspaceId%22%3A%22maroon-moth-0zrxd0wz%22%2C%22gitpodHost%22%3A%22https%3A%2F%2Fgitpod.io%22%7D
[10/29/2021, 10:53:46 AM] acquiring lock: gitpod.io
[10/29/2021, 10:53:46 AM] acquired lock: gitpod.io
[10/29/2021, 10:53:46 AM] fetching the local app from https://gitpod.io/static/bin/gitpod-local-companion-darwin
[10/29/2021, 10:53:46 AM] released lock: gitpod.io
[10/29/2021, 10:53:47 AM] failed to access the local app: Error: workspace not found
[10/29/2021, 10:53:47 AM] failed to open uri: Error: workspace not found
Even If one user shares the workspace the other can not open it locally
Steps to reproduce
User two different Bitbucket-Accounts with two different gitpod accounts try to open their private projects on the same vscode app locally - if you are logged in to vscode and sync your settings it is even not possible to delete ~/.vscode to get this working - after login all the old stuff and the token is there again.
Workspace affected
No response
Expected behavior
1.) Use different bitbucket/github/gitlab accounts with the same gitpod user.
2.) Open All Projects locally in VSCode with the login from the browser.
Example repository
No response
Anything else?
Let me know if I can help.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure in VSCode Desktop or VSCode Insiders with two Gitpod accounts and review the local companion log, especially the “workspace not found” error. Use the workspace URI shown in the report as the reproduction entry point. Done means both accounts can open their private workspaces locally, including a shared workspace, without restoring the wrong account token.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- authentication, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100