🐛(frontend) make the device-in-use logic race-free

The device-in-use logic could race when multiple detection events fired close together (e.g. rapid mic/cam toggles or several devices becoming busy at once), leading to inconsistent store state. Refactor the flow so all updates go through a serialized path, removing the race conditions and keeping the in-use state consistent regardless of event ordering.
♻️(frontend) track device-in-use state by id instead of by kind
2026-09-02 13:48:26 +00:00 · 2026-08-23 17:14:17 +02:00 · 2026-08-23 16:47:05 +02:00 · 2026-08-23 16:10:06 +02:00 · 2026-08-23 16:10:05 +02:00 · 2026-08-23 16:10:05 +02:00
13 changed files with 14 additions and 23 deletions
@@ -8,8 +8,6 @@ and this project adheres to
 ## [Unreleased]
 ## [1.28.0] - 2026-08-24
 ### Added
 - 📈(frontend) track errors when starting or stopping a recording
@@ -37,7 +35,6 @@ 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
@@ -1,7 +1,7 @@
 [project]
 name = "agents"
-version = "1.28.0"
+version = "1.27.0"
 requires-python = ">=3.12"
 dependencies = [
    "livekit-agents==1.6.7",
@@ -9,7 +9,7 @@ resolution-markers = [
 [[package]]
 name = "agents"
-version = "1.28.0"
+version = "1.27.0"
 source = { virtual = "." }
 dependencies = [
    { name = "livekit-agents" },
@@ -7,7 +7,7 @@ build-backend = "uv_build"
 [project]
 name = "meet"
-version = "1.28.0"
+version = "1.27.0"
 authors = [{ "name" = "DINUM", "email" = "dev@mail.numerique.gouv.fr" }]
 classifiers = [
    "Development Status :: 5 - Production/Stable",
@@ -1187,7 +1187,7 @@ wheels = [
 [[package]]
 name = "meet"
-version = "1.28.0"
+version = "1.27.0"
 source = { editable = "." }
 dependencies = [
    { name = "aiohttp" },
@@ -1,12 +1,12 @@
 {
  "name": "meet",
-  "version": "1.28.0",
+  "version": "1.27.0",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {
      "name": "meet",
-      "version": "1.28.0",
+      "version": "1.27.0",
      "dependencies": {
        "@fontsource-variable/atkinson-hyperlegible-next": "5.2.6",
        "@fontsource-variable/lexend": "5.2.11",
@@ -1,7 +1,7 @@
 {
  "name": "meet",
  "private": true,
-  "version": "1.28.0",
+  "version": "1.27.0",
  "type": "module",
  "scripts": {
    "dev": "panda codegen && vite",
@@ -2,12 +2,6 @@ import type { CaptureResult } from 'posthog-js'
 const IGNORED_EXCEPTION_PATTERNS = [
  /ResizeObserver loop (completed with undelivered notifications|limit exceeded)/,
  // livekit-client leaks the raw WebSocket error Event as an unhandled
  // rejection when the signal ws errors after connect (Firefox-heavy,
  // coincides with signal reconnects). Carries zero diagnostic content —
  // the close reason is already logged by the SDK.
  // See: https://github.com/livekit/client-sdk-js/issues/2062
  /^Event captured as exception with keys: isTrusted$/,
 ]
 const shouldIgnoreException = (value: unknown): boolean =>
@@ -1,12 +1,12 @@
 {
  "name": "mail_mjml",
-  "version": "1.28.0",
+  "version": "1.27.0",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {
      "name": "mail_mjml",
-      "version": "1.28.0",
+      "version": "1.27.0",
      "license": "MIT",
      "dependencies": {
        "@html-to/text-cli": "0.6.1",
@@ -1,6 +1,6 @@
 {
  "name": "mail_mjml",
-  "version": "1.28.0",
+  "version": "1.27.0",
  "description": "An util to generate html and text django's templates from mjml templates",
  "type": "module",
  "dependencies": {
@@ -1,12 +1,12 @@
 {
  "name": "sdk",
-  "version": "1.28.0",
+  "version": "1.27.0",
  "lockfileVersion": 3,
  "requires": true,
  "packages": {
    "": {
      "name": "sdk",
-      "version": "1.28.0",
+      "version": "1.27.0",
      "license": "ISC",
      "workspaces": [
        "./library",
@@ -1,6 +1,6 @@
 {
  "name": "sdk",
-  "version": "1.28.0",
+  "version": "1.27.0",
  "author": "",
  "license": "ISC",
  "description": "",
@@ -1,7 +1,7 @@
 [project]
 name = "summary"
-version = "1.28.0"
+version = "1.27.0"
 dependencies = [
    "fastapi[standard]>=0.105.0",
    "uvicorn>=0.24.0",
Author	SHA1	Message	Date
lebaudantoine	bcd95da21f	🐛(frontend) make the device-in-use logic race-free The device-in-use logic could race when multiple detection events fired close together (e.g. rapid mic/cam toggles or several devices becoming busy at once), leading to inconsistent store state. Refactor the flow so all updates go through a serialized path, removing the race conditions and keeping the in-use state consistent regardless of event ordering.	2026-08-23 17:14:17 +02:00
lebaudantoine	38f3f9f52d	♻️(frontend) track device-in-use state by id instead of by kind Refactor the device-in-use handling to key state by device id instead of only by kind (microphone or camera). On computers with several devices of the same kind, keying by kind meant that one device being in use marked the whole kind as busy, even when the user could still use another device. Tracking per id lets the UI and logic distinguish between devices correctly. The store is updated accordingly so that per-device state is stored and read consistently across the app.	2026-08-23 16:47:05 +02:00
lebaudantoine	3ec1627e25	🐛(frontend) treat "Timeout starting source" AbortError as device-in-use Also consider `AbortError` with a message like "Timeout starting video/audio source" as an "already in use" device error. This can happen for other reasons in theory, but in practice most occurrences are caused by another application still holding the camera or microphone. Route it through the existing device-in-use handling so users get the same clear explanation as with the standard error, instead of a generic failure.	2026-08-23 16:10:06 +02:00
lebaudantoine	2e31947bad	🐛(frontend) handle Firefox/Windows AbortError on device start Some versions of Firefox on Windows do not raise the `NotReadableError` that LiveKit expects when the camera or microphone fails to start. Instead, they surface an `AbortError` with a message explaining the browser could not start the video or microphone input. This case was observed in PostHog error tracking and was not handled, so users hit an unhelpful failure state. Detect that specific `AbortError` and route it through the same device-in-use / not-readable handling as the standard error, so users get a clear explanation.	2026-08-23 16:10:05 +02:00
lebaudantoine	54e9747350	🐛(frontend) handle device-in-use errors on Chrome / Windows 10 On Chrome and Windows 10, when the camera or microphone is already in use by another application, the browser rejects `getUserMedia`. Without dedicated handling, users just saw their camera or microphone not turning on, without any explanation. Detect this specific failure and surface a clear message to the user, so they understand another application is holding the device and know what to do about it.	2026-08-23 16:10:05 +02:00