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
Describe the bug
This happens when a user changes the network on the fly. When switching networks, the socket.io client goes from connected to disconnected to reconnected state. But the actual socket does not send or receive data for a lot longer (normally 30-45 seconds)
Additional info: The socket.io server is behind nginx.
To Reproduce
Client side, connect to the socket.io server
Switch networks (If you have multiple Wifi networks, you can switch to another network, on phone you can switch between wifi and cellular network)
Sometimes the socket.io client emits the disconnected event
After the network is changed, normally in less than 5 seconds the reconnect event is emitted
The socket is not actually connected, messages cannot be sent/received from the server, messages are instead queued, normally after 30-45 seconds post the reconnect event, messages start flowing as usual.
Please fill the following code example:
Socket.IO server version: 4.7.2
Socket.IO client version: 4.7.2
Expected behavior
The client socket must be actually connected when it emits the reconnect event.
On a slightly off topic note, v4 of socket.io has been a joy to develop with. Thank you to all socket.io maintainers.
The text was updated successfully, but these errors were encountered:
Have tested on Android chrome 117, and Mac chrome 117.
One small change is that i have only one network interface open at a time. So the device has wifi on, cellular data off, then i switch off wifi and turn on cellular data
Describe the bug
This happens when a user changes the network on the fly. When switching networks, the socket.io client goes from connected to disconnected to reconnected state. But the actual socket does not send or receive data for a lot longer (normally 30-45 seconds)
Additional info: The socket.io server is behind nginx.
To Reproduce
Please fill the following code example:
Socket.IO server version:
4.7.2
Socket.IO client version:
4.7.2
Expected behavior
The client socket must be actually connected when it emits the reconnect event.
On a slightly off topic note, v4 of socket.io has been a joy to develop with. Thank you to all socket.io maintainers.
The text was updated successfully, but these errors were encountered: