@limrun/ui 0.9.0-rc.13 → 0.9.0-rc.14

package/dist/components/remote-control.d.ts

@@ -94,33 +94,25 @@ interface RemoteControlProps {
      */
     axMaxBackoffMs?: number;
     /**
-     * Optional outbound camera input.
+     * Fires whenever the iOS simulator's camera demand state changes —
+     * i.e. an app inside the sim called
+     * `[AVCaptureSession startRunning]` or `[stopRunning]`. The
+     * component handles the `navigator.mediaDevices.getUserMedia` prompt
+     * and SDP plumbing internally; this callback is purely so the host
+     * UI can render a status indicator ("simulator is using your
+     * camera", etc.).
      *
-     * When provided, every video track on this `MediaStream` is forwarded
-     * up the same `RTCPeerConnection` that already carries the device
-     * screen downstream. On iOS instances, the limulator-side injector
-     * splices those frames into apps that use AVFoundation, so the user's
-     * browser camera becomes the iOS camera (`AVCaptureDevice.default(for:
-     * .video)`).
+     * `active` reflects whether the sim is currently asking for
+     * frames. `granted` is set only on the call that follows a
+     * `getUserMedia` attempt: `true` when the user accepted the
+     * browser prompt, `false` when they denied or the call failed
+     * (in which case the limulator side switches to a black-frame
+     * fallback so the app keeps ticking).
      *
-     * Today this is only honored by iOS instances launched with the
-     * camera runtime; Android instances ignore it.
-     *
-     * Lifecycle expectations:
-     * - Pass `null`/`undefined` to skip outbound camera (default).
-     * - Pass a `MediaStream` obtained from
-     *   `navigator.mediaDevices.getUserMedia({ video: true })` (or any
-     *   other source — screen capture, virtual camera, etc.).
-     * - Changing the `MediaStream.id` triggers a connection restart so
-     *   the new track is included in the SDP offer. The reference itself
-     *   is allowed to be unstable across renders — we key the reconnect
-     *   on `id`, not object identity, so memoization isn't required.
-     * - Stopping the tracks (e.g. `track.stop()`) on the parent side is
-     *   sufficient to cut the outbound feed without restarting; the peer
-     *   connection just stops getting frames on that track. To fully
-     *   detach the track from the SDP, swap the prop to `null`.
+     * Only iOS instances ever fire this callback; Android instances
+     * have no camera-injector path and stay silent.
      */
-    cameraStream?: MediaStream | null;
+    onCameraDemandChange?: (active: boolean, granted?: boolean) => void;
 }
 interface ScreenshotData {
     dataUri: string;