If you don't move for a while (during a conversation) the websockets connection seems to timeout, and no further location updates are received. This has to be fixed before it can be used live, because people become desynced and will miss the presence of newly joined users.
Not sure we can just up the timeout thresholds, or we will need a periodic ping.
app.js:232 WebSocket is already in CLOSING or CLOSED state.
If you don't move for a while (during a conversation) the websockets connection seems to timeout, and no further location updates are received. This has to be fixed before it can be used live, because people become desynced and will miss the presence of newly joined users.
Not sure we can just up the timeout thresholds, or we will need a periodic ping.
app.js:232 WebSocket is already in CLOSING or CLOSED state.