-
Notifications
You must be signed in to change notification settings - Fork 32
Reconnect fails #17
Comments
Yeah, I get this problem too. So far I have not been able to fix this problem. Is it a problem on the server-side or client-side? Because after restarting the client-side, the connection works fine. :/ |
I'm pretty sure it's client side @NicoAiko. I've used my NodeJS server many times in the past along with the JS Library from Socket.IO and I never had this issue. |
@sinokgr Which version of |
@NicoAiko , you mean for the server? and old version, it wasn't working with the new versions at all for me. I'm not at the PC with that code at the moment to check specifically. |
Because I use NestJS v7 which uses Socket.IO v2. There is the possibility that SocketIOSharp, which uses v4 (at least if I interpret it correctly) is not fully compatible and the reconnect functionality is not working for that reason. I have yet to check if Socket.IO v4 (server-side) works or not though. |
I checked with v4 of the socket.io server nodejs package and yeah... it didn't work. It'll probably be necessary to change the client package to another one. |
Hi All,
I'm trying SocketIOSharp on mini project I'm working on, and I'm having one issue. Every time I restart the server, I'm getting an error.
Node.JS server below.
Error
Any ideas why this happening? Reconnect default settings seem fine, so I'm a bit confused. I searched online but I didn't find anything similar.
Many thanks,
Nick
The text was updated successfully, but these errors were encountered: