M3DZIK/discordrpc

Socket Error: This socket has been ended by the other party

SkyEmie opened this issue · 5 comments

SkyEmie commented

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

M3DZIK commented

Hmm, I'll check it out later.

  • 👍2
xqtc161 commented

Hi, same for me. I guess the last update broke it.

[RPCServer:IPC] Socket Opened: 5248
eb8dfda….js:149 [RPCServer:IPC] Socket Close: 5248
eb8dfda….js:149 [RPCServer:IPC] Socket Emit: 5248 
  {cmd: "DISPATCH", data: {…}, evt: "READY", nonce: null}
  cmd: "DISPATCH"
  data: {v: 1, config: {…}, user: {…}}
  evt: "READY"
  nonce: null
  __proto__: Object
eb8dfda….js:149 [RPCServer:IPC] Socket Error: This socket has been ended by the other party

(Edit 1)
Might be an issue with the discord_rich_presence crate you are using to connect to Discord...

M3DZIK commented

(Edit 1) Might be an issue with the discord_rich_presence crate you are using to connect to Discord...

I think rather yes.

SkyEmie commented

Do you think you will fix this, or do I need to find an another solution?

xqtc161 commented

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.