-
Notifications
You must be signed in to change notification settings - Fork 21
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 doesn't work with the Snap images #25
Comments
Can verify this issue a month after it was originally posted. Regards. |
This seems to still be a problem. Could this get looked into? |
@Blackop778 check the linked issues might offer some workaround for you |
seems to work with the system-observe connection |
I've tested with |
It works for spotify snap <-> discord snap |
Tested also with intellij and android-studio - discord rich presence does really not work with vscode, and those two apps (works for spotify though, maybe because spotify is not classic?). Would be great if this could be somehow fixed and I think this issue needs to be re-opened |
Sorry for the poke, but this issue is sadly still remaining. While the rich presence of other confined snaps like spotify can be seen in the discord snap, the connection to the vscode and intellij snaps rich presence is still not working. I would thus vote to re-open this issue |
Per discord/discord-rpc the IPC uses a UNIX socket in |
Noticed today that the discord snap rich presence now works with this extension! 🥳 |
Thanks for reporting this, everyone! Closing this issue again, as it seems to be fixed according to @Feichtmeier 's comment. If you find apps where it's not working, please comment and we can reopen this issue! |
When trying to use any Discord RPC enabled application together with the Snap images of Discord the rich presence doesn't show up. As soon as you switch to the Debian package provided by Discord on their website everything works as expected.
Tested on Ubuntu 18.04 LTS with Discord Snap Version 0.0.4
The text was updated successfully, but these errors were encountered: