In some cases, the WebSocket disconnects and does not reconnect

[boxmein]

We have seen a case where the WebSocket disconnects and does not reconnect. We're still investigating / discovering the correct root cause.

[boxmein]

The Javascript API will use various features (#331 #435 #440 #548 #576 #577 #582) to detect if the WebSocket connection should be discarded. It then opens a new WebSocket connection and re-establishes the GraphQL subscriptions on the new socket.

[boxmein]

The WebSocket backend will send a close code of 1005 to the client when it is being deployed. The close code 1005 will cause a handleConnectionDrop and trigger an immediate re-connection.

[boxmein]

It looks like in some cases there is a logged event of "connection closed with code 1000". Is the server initiating a close with the code 1000?

[boxmein]

Using regular macOS settings, causing a disconnect and reconnect of the wifi will correctly recreate the WebSocket.

Perhaps it's a timing bug of some sort?

[boxmein]

Version 11.2.0 changes the behavior of the WebSocket to retry when the socket is closed with a code of 1000.