🔇(frontend) suppress leaked WebSocket error events from livekit-client

livekit-client leaks the raw WebSocket error Event as an unhandled
rejection when the signal WebSocket errors after connect. This is
mostly seen on Firefox and coincides with signal reconnects.

The event carries zero diagnostic content — the close reason is
already logged by the SDK — so it only adds noise to error
tracking.

Filter it out from our reporting.

Upstream issue: https://github.com/livekit/client-sdk-js/issues/2062
This commit is contained in:
lebaudantoine
2026-08-23 17:58:05 +02:00
parent 84845709d0
commit 14bb3e6400
2 changed files with 7 additions and 0 deletions
+1
View File
@@ -35,6 +35,7 @@ and this project adheres to
- 🐛(frontend) handle device-in-use errors on Chrome / Windows 10
- 🐛(frontend) handle Firefox/Windows AbortError on device start
- 🐛(frontend) treat "Timeout starting source" AbortError as device-in-use
- 🔇(frontend) suppress leaked WebSocket error events from livekit-client
## [1.27.0] - 2026-08-14