This repository has been archived by the owner on Oct 20, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Socket Error: This socket has been ended by the other party #68
Comments
Hmm, I'll check it out later. |
Hi, same for me. I guess the last update broke it.
(Edit 1) |
I think rather yes. |
Do you think you will fix this, or do I need to find an another solution? |
It's not really up to them if the crate they are using is outdated/needs to be fixed. You might want to turn to the developers of the Discord Rich Presence crate which is being used here to bring this issue to their attention. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
Well done for this contribution, so I wanted to give a try with this little cli utility.
I created the application, copy the client id, then added only the detail field
The connection seems to work, I can see the RPC/IPC call received in the discord devtool, and discordrpc shows "Connected!"
But nothing is displayed on my profile, and a second later, discord throws the following error:
[RPCServer:IPC] Socket Error: This socket has been ended by the other party
Is your utility compatible with the latest version of discord?
Best regards,
Emie
The text was updated successfully, but these errors were encountered: