[Bug]: Discord RPC stops working if you change Client Name - Githubissues

ciderapp / Cider-2

Primary public repository for Cider 2.x

https://cider.sh

128 stars 2 forks source link

[Bug]: Discord RPC stops working if you change Client Name #441

Closed IsaacMarovitz closed 7 months ago

IsaacMarovitz commented 8 months ago

Preflight Checklist

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for a bug report that matches the one I want to file, without success.
[X] I have read the troublshooting FAQs and none solved my issue.

What operating system are you using?

macOS

Build Details

Version 2.2.0 (Built 21/09/2023)

Operating System Version

macOS Sonoma 14.1

Describe the Bug

If you change the Client Name in Cider settings, Discord RPC will stop working till you next relaunch Cider.

Steps to Reproduce

Change Client Name (e.g. Cider -> Cider 2)
Discord RPC stops displaying
Relaunch Cider
Discord RPC works again with new name

Anything else?

No response

Connect Device ID

No response

Build timestamp

No response

coredev-uk commented 7 months ago

This is probably the case of an RPC connection timeout. DiscordRPC is a bit funky sometimes and prevents 2 client IDs from the same application. I recommend a restart after changing the client ID. Not much more can be done on our end, this is how Discord does it and changing the client ID is not standard expected behaviour from an application.