You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the connection to server is lost, this error start spamming the console every 1 min. Is there a way to drop the disconnect handshake and force close the socket?
OnError: System.Net.WebSockets.WebSocketException (0x80004005): The remote party closed the WebSocket connection without completing the close handshake. ---> System.IO.IOException: Unable to write data to the transport connection: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. . ---> System.Net.Sockets.SocketException: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.
Really cool socket,io library btw!!
The text was updated successfully, but these errors were encountered:
enrickla
changed the title
Stuck when lose the connection
Cannot disconnect if the connection is lost
Aug 24, 2020
Hi,
When the connection to server is lost, this error start spamming the console every 1 min. Is there a way to drop the disconnect handshake and force close the socket?
OnError: System.Net.WebSockets.WebSocketException (0x80004005): The remote party closed the WebSocket connection without completing the close handshake. ---> System.IO.IOException: Unable to write data to the transport connection: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. . ---> System.Net.Sockets.SocketException: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.
Really cool socket,io library btw!!
The text was updated successfully, but these errors were encountered: