@displayxr/inline3d 1.47.3 → 1.47.5

package/CHANGELOG.md

@@ -5,6 +5,48 @@ entry points (`.`, `./three`) are frozen for 1.x, while the **scene subpaths** (
 `./splat`, `./model`) are a preview tier whose options may change in any release. Entries below say
 which tier they touch, because that is what tells you whether an upgrade can move your pixels.
 
+## Unreleased
+
+## 1.47.5 — 2026-11-01
+
+### Fixed — the camera permission prime could open a phone lens and crash its camera (`./camera`, `./call`)
+
+Before camera permission, `openCamera('auto')` primed on `{1280x720, facingMode: 'environment'}`.
+On a phone whose lenses all report the same facing, that picked camera 0, one lens of the 3D
+camera's pair, and on some phones a plain open of that lens, or its teardown, crashes the camera
+service. The prime now asks for the default camera with no constraints. The DisplayXR Browser lists
+its 3D camera first, so the prime opens the pair directly and no lens is opened. A desktop webcam is
+still opened once and kept, and is then asked for the usual 1280x720 mode without a second start.
+With labels visible but no 3D camera listed, the list is read once more before the fallback, since
+a runtime 3D camera can appear late after a runtime restart.
+
+## 1.47.4 — 2026-10-31
+
+### Fixed — a declared 3D camera with portrait eyes was dropped for a plain one (`./camera`, `./call`)
+
+- `openCamera` kept a device as a pair only if it was wider than 2.5:1. A phone's front pair with
+  portrait eyes (720x1280 each, so a 1440x1280 frame) failed that test: the SDK stopped the
+  "3D Camera (DisplayXR)" track and fell back to the plain default camera. A track whose settings
+  say `displayxrStereo.layout === 'side-by-side'` is now a pair whatever its aspect, so the SDK no
+  longer falls back once the browser offers a stereo track. Shape is still the guess for devices
+  that say nothing (USB pairs).
+
+### Fixed — before camera permission, `openCamera` opened a phone's front (head-tracker) lens (`./camera`, `./call`)
+
+Touches `./camera` (`openCamera`'s `auto` / `stereo` probe) and so `./call`'s camera. With camera
+permission already granted, nothing changes.
+
+- Without permission the device labels are empty, so the probe used to open the platform default
+  camera just to get them: on a phone that is the front lens the head tracker holds, and opening
+  it coincided with every camera dropping out for about 2.4 s. It now primes permission on an
+  environment-facing camera (`facingMode: { ideal: 'environment' }`), reads the list again, and
+  opens a camera that names itself stereo **by id before the default**. A desktop webcam that
+  reports no facing is opened once and kept as the mono fallback (no extra camera start); a phone
+  with no pair still falls back to the default (front) camera for a self view.
+- `camera-busy` now reads "camera unavailable: in use by another app (e.g. eye tracking) or unable
+  to deliver a picture". A 3D camera that is listed but cannot deliver also fails with
+  `NotReadableError`, so "every camera is in use" was wrong for it.
+
 ## 1.47.3 — 2026-10-31
 
 ### Fixed — a rear 3D camera's view was mirrored (`./camera`, `./call`)