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

Discord Rich Presence extension because it depends on the 'Git' extension #323

Closed
yMaatheus opened this issue Jun 5, 2024 · 7 comments
Closed

Comments

@yMaatheus
Copy link

image

The extension stopped working out of nowhere and is giving this error. I don't know what it could be since git is loading normally

@Therkelsen
Copy link

Had the same issue, you can downgrade the extension temporarily until there's a fix for it:

  1. Press Ctrl + Shift + X to open the Extensions sidebar.
  2. Search for “Discord Rich Presence”.
  3. Click on the extension.
  4. Click on the arrow next to “Uninstall”.
  5. Select “Install Another Version”.
  6. Choose v5.2.10.
  7. Restart your VS Code / development container.

@nick22985
Copy link
Collaborator

nick22985 commented Jun 6, 2024

This seems like a vscode issue. Git should always bw a lodes extension as it comes woth vscode.

@Therkelsen
Copy link

This seems like a vscode issue. Git should always bw a lodes extension as it comes woth vscode.

Not sure I agree, as downgrading the extension fixes it.

@nick22985
Copy link
Collaborator

nick22985 commented Jun 6, 2024

Git not being present caused other issues. We made it a dependency so vscode would force start vscode.git before vscord. This is shipped by default with VSCode (see #320)

  1. Try enabling the extension manually. You should be able to view the inbuilt extensions by running Extensions: Show Built-in Extensions from the command available
  2. What Version of vs code are you running?
  3. Are you developing with the remote extension?
  4. what are the Minimal extensions / steps so we can recreate this?

@yMaatheus
Copy link
Author

@Therkelsen it worked, thanks! 😄

@leonardssh
Copy link
Owner

@nick22985 I've just revert your commit and release a patch version. We can investigate further why it doesn't work for everyone.

@nick22985
Copy link
Collaborator

nick22985 commented Jun 7, 2024

@leonardssh I am almost certain this bug with vscode or an extension that currently does not have support

microsoft/vscode#85177 - was the issue I found on vscode but was closed and made on the extension repo. Issues on that repo are here:
https://bitbucket.org/atlassianlabs/atlascode/issues/278/cannot-activate-the-extension-because-it
https://bitbucket.org/atlassianlabs/atlascode/issues/169/unhandled-dependency-issue-during-ssh

Which links back to the main issue with discussion in it: https://bitbucket.org/atlassianlabs/atlascode/issues/112/support-for-vs-code-remote-development

there is also this where it was an issue for a certain version of insiders build of vscode: https://bitbucket.org/atlassianlabs/atlascode/issues/279/cannot-activate-the-jira-and-bitbucket

The only thing I can think of is that it is because the remote extension is being used, but this works for me without issue. So, if they are running it remotely, we might need to add support for the remote extension, which the link above does say how to do but needs more info.

microsoft/vscode#159421

Also saw this were if using remote and it is in two environments would cause this issue

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

4 participants