Network disconnect / offline mode not detected

[hyperknot]

Describe the bug
When turning off the wireless network on my MacBook, the client does not detect the disconnect event. It waits a possibly long time until the ping detects it. Using Websockets.

To Reproduce
Any basic example will replicate it, for example https://socket.io/demos/chat/ replicates it.

Server
Does not matter, it is disconnected on the client.

Socket.IO client version: 3.0.4

Client

Default options, only auth is specified in options.

Expected behavior
A clear and concise description of what you expected to happen.

When disconnecting the network, the socket should detect a disconnect event.
The browser correctly recognizes such event, the following triggers immediately.

window.addEventListener('offline', () => {alert('offline')});

navigator.onLine is also correctly showing false.

However SocketIO client believes it is still connected, the WS connection is sending messages like everything was connected. Only after the next ping event it recognizes that something is wrong and fires the disconnect event.

Platform:

• Device: Macbook Pro
• OS: macOS 10.15.7
• Browser: latest Chrome and Firefox

[hyperknot]

As a workaround, is there a way to force-send a ping event?

[hyperknot]

So far I came up with this workaround, this seems to work.

    window.addEventListener('offline', () => {
      if (
        this.socket &&
        this.socket.io &&
        this.socket.io.engine &&
        this.socket.io.engine.transport
      ) {
        this.socket.io.engine.transport.close()
      }
    })

How do everyone else handle this problem?

[dverzolla]

Fixed in 3.0.5: bcdd3be#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed

[darrachequesne]

@dverzolla I don't think this is fixed yet.

@hyperknot I could indeed reproduce, thanks. That's really weird, one could expect that the TCP connection would be closed when the network is turned off, but that does not seem to be the case.

[darrachequesne]

This should be fixed by socketio/engine.io-client@c361bc6, included in [email protected].

Thanks for the detailed bug report 👍