Matthew Hodgson f2eabed7ae Say "Server unavailable" for signal-only reconnects instead of muting the call ...

When the SFU drops the signalling WebSocket, livekit-client resumes it
while the peer connection stays up and media keeps flowing. EC treated
this as a full reconnect: playback volume zeroed on every remote tile,
remote video hidden, and the non-dismissable Reconnecting scrim shown,
so a 2 s blip silenced the whole call.

LocalMember now exposes signalReconnecting$ separately and no longer
counts SignalReconnecting as a disconnect, so reconnecting$ (and with it
pretendToBeDisconnected$, the hands/reactions pause and the reconnect
analytics) only fires for a real Reconnecting, a disconnect or a
homeserver problem. InCallView shows a scrimless, non-modal "Server
unavailable" toast for the signal-only case so the user still gets
told what is going on, per the review of the first attempt.

2026-09-29 11:51:29 +01:00

..

app.json

Say "Server unavailable" for signal-only reconnects instead of muting the call

2026-09-29 11:51:29 +01:00