react-native-image-stitcher 0.12.0 → 0.14.0

package/dist/camera/CaptureHeader.js

@@ -27,20 +27,26 @@ exports.CaptureHeader = CaptureHeader;
 const react_1 = __importDefault(require("react"));
 const react_native_1 = require("react-native");
 function CaptureHeader({ title, onBack, backLabel = '‹ Back', onSettingsPress, guidance, topInset = 0, colors, style, }) {
-    const bg = colors?.background ?? '#000000';
+    // v0.13.1 — defaults are now transparent over the camera preview
+    // (matches the AR toggle / settings gear pill style); hosts using
+    // the header outside a camera context can pass solid colours via
+    // `colors`.  Title + gear get a text shadow for legibility over
+    // bright preview content; guidance row keeps a translucent pill
+    // background for the same reason.
+    const bg = colors?.background ?? 'transparent';
     const titleColor = colors?.title ?? '#ffffff';
     const accent = colors?.accent ?? '#FF9F0A';
-    const guidanceBg = colors?.guidanceBackground ?? 'rgba(255,255,255,0.08)';
+    const guidanceBg = colors?.guidanceBackground ?? 'rgba(0,0,0,0.45)';
     const guidanceColor = colors?.guidanceText ?? '#ffffff';
     return (react_1.default.createElement(react_native_1.View, { style: [{ backgroundColor: bg }, style] },
-        react_1.default.createElement(react_native_1.View, { style: [styles.titleRow, { paddingTop: topInset + 8 }] },
+        react_1.default.createElement(react_native_1.View, { style: [styles.titleRow, { paddingTop: topInset + 4 }] },
             onBack ? (react_1.default.createElement(react_native_1.Pressable, { onPress: onBack, hitSlop: 12, accessibilityRole: "button", accessibilityLabel: "Go back", style: styles.backButton },
-                react_1.default.createElement(react_native_1.Text, { style: [styles.backText, { color: accent }] }, backLabel))) : (
+                react_1.default.createElement(react_native_1.Text, { style: [styles.backText, styles.textShadow, { color: accent }] }, backLabel))) : (
             // Empty spacer keeps the title centred even when back is hidden.
             react_1.default.createElement(react_native_1.View, { style: styles.backButton })),
-            react_1.default.createElement(react_native_1.Text, { style: [styles.title, { color: titleColor }], numberOfLines: 1, accessibilityRole: "header" }, title),
+            react_1.default.createElement(react_native_1.Text, { style: [styles.title, styles.textShadow, { color: titleColor }], numberOfLines: 1, accessibilityRole: "header" }, title),
             onSettingsPress ? (react_1.default.createElement(react_native_1.Pressable, { onPress: onSettingsPress, hitSlop: 12, accessibilityRole: "button", accessibilityLabel: "Open panorama settings", style: styles.backButton },
-                react_1.default.createElement(react_native_1.Text, { style: [styles.gearIcon, { color: accent }] }, "\u2699"))) : (react_1.default.createElement(react_native_1.View, { style: styles.backButton }))),
+                react_1.default.createElement(react_native_1.Text, { style: [styles.gearIcon, styles.textShadow, { color: accent }] }, "\u2699"))) : (react_1.default.createElement(react_native_1.View, { style: styles.backButton }))),
         guidance ? (react_1.default.createElement(react_native_1.View, { style: [styles.guidance, { backgroundColor: guidanceBg }], accessibilityRole: "text" },
             react_1.default.createElement(react_native_1.Text, { style: [styles.guidanceText, { color: guidanceColor }], numberOfLines: 2 }, guidance))) : null));
 }
@@ -49,33 +55,50 @@ const styles = react_native_1.StyleSheet.create({
         flexDirection: 'row',
         alignItems: 'center',
         justifyContent: 'space-between',
-        paddingHorizontal: 16,
-        paddingBottom: 8,
+        paddingHorizontal: 12,
+        paddingBottom: 4,
     },
     backButton: {
-        minWidth: 64,
-        paddingVertical: 4,
+        minWidth: 56,
+        paddingVertical: 2,
     },
     backText: {
-        fontSize: 16,
+        fontSize: 14,
         fontWeight: '500',
     },
     title: {
         flex: 1,
         textAlign: 'center',
-        fontSize: 16,
+        fontSize: 14,
         fontWeight: '600',
     },
     guidance: {
-        paddingHorizontal: 16,
-        paddingVertical: 8,
+        // v0.13.1 — guidance row is now a centred pill inset from the
+        // edges (matches the AR-toggle / lens-chip pill style) rather
+        // than a full-width band.  The pill background gives it its
+        // own contrast over the preview without forcing a solid bar.
+        alignSelf: 'center',
+        marginTop: 4,
+        paddingHorizontal: 10,
+        paddingVertical: 5,
+        borderRadius: 12,
+        maxWidth: '90%',
     },
     guidanceText: {
-        fontSize: 13,
+        fontSize: 12,
+        textAlign: 'center',
     },
     gearIcon: {
-        fontSize: 22,
+        fontSize: 20,
         textAlign: 'right',
     },
+    // v0.13.1 — subtle text shadow so the (now-transparent) header
+    // text stays legible over bright preview content.  Same trick
+    // iOS Camera uses for the timestamp / mode labels.
+    textShadow: {
+        textShadowColor: 'rgba(0,0,0,0.65)',
+        textShadowOffset: { width: 0, height: 1 },
+        textShadowRadius: 2,
+    },
 });
 //# sourceMappingURL=CaptureHeader.js.map

package/dist/camera/CapturePreview.js

@@ -37,7 +37,19 @@ function CapturePreview({ visible, imageUri, imageWidth, imageHeight, actions, o
         ? imageWidth / imageHeight
         : 16 / 9;
     const hasActions = actions && actions.length > 0;
-    return (react_1.default.createElement(react_native_1.Modal, { visible: visible, animationType: "fade", transparent: true, statusBarTranslucent: true, onRequestClose: onClose },
+    return (react_1.default.createElement(react_native_1.Modal, { visible: visible, animationType: "fade", transparent: true, statusBarTranslucent: true, 
+        // v0.13.1 — RN's iOS <Modal> defaults to portrait-only, which
+        // pins the stitched-image preview to portrait even when the host
+        // app is in landscape (the preview appeared sideways/letterboxed
+        // under a non-locked host).  Declaring all four keeps the modal
+        // aligned with the interface.  Mirrors the v0.12 fix already on
+        // OrientationDriftModal + PanoramaSettingsModal.
+        supportedOrientations: [
+            'portrait',
+            'portrait-upside-down',
+            'landscape-left',
+            'landscape-right',
+        ], onRequestClose: onClose },
         react_1.default.createElement(react_native_1.View, { style: styles.backdrop },
             react_1.default.createElement(react_native_1.View, { style: styles.topBar },
                 react_1.default.createElement(react_native_1.View, { style: styles.topBarSpacer }),

package/dist/camera/CaptureThumbnailStrip.d.ts

@@ -82,6 +82,30 @@ export interface CaptureThumbnailStripProps {
      * stay under the strip's control to keep the count line consistent.
      */
     style?: StyleProp<ViewStyle>;
+    /**
+     * v0.13.1 — when `true`, the strip stacks thumbnails VERTICALLY
+     * (column, scrolls up/down) instead of the default horizontal row.
+     * `<Camera>` sets this from the same `isSideEdge(homeIndicatorEdge)`
+     * signal that drives PanoramaBandOverlay's `vertical`, so under a
+     * non-locked host in landscape the idle capture strip stacks along
+     * the home-indicator edge like the live band does (rather than
+     * running horizontally across the middle of the rotated screen).
+     * Default `false` (legacy horizontal strip) — unchanged for
+     * portrait-locked hosts.
+     */
+    vertical?: boolean;
+    /**
+     * v0.13.1 — counter-rotation applied to each thumbnail image so the
+     * captured scene reads upright when the device is held landscape
+     * under a PORTRAIT-LOCKED host (the JS framebuffer stays portrait, so
+     * the thumbnail would otherwise show 90° off).  `<Camera>` passes the
+     * `useContentRotation()` result; `{}` (no-op) in upright cases.
+     * Applies only to the strip's own images — orientation of the strip's
+     * scroll axis is handled separately by `vertical`.
+     */
+    contentRotation?: {
+        transform?: ViewStyle['transform'];
+    };
 }
-export declare function CaptureThumbnailStrip({ items, minPhotos, maxPhotos, backgroundColor, textColor, successColor, warningColor, disablePreview, onItemPress, style, }: CaptureThumbnailStripProps): React.JSX.Element;
+export declare function CaptureThumbnailStrip({ items, minPhotos, maxPhotos, backgroundColor, textColor, successColor, warningColor, disablePreview, onItemPress, style, vertical, contentRotation, }: CaptureThumbnailStripProps): React.JSX.Element;
 //# sourceMappingURL=CaptureThumbnailStrip.d.ts.map

package/dist/camera/CaptureThumbnailStrip.js

@@ -91,7 +91,7 @@ function thumbWidth(item) {
     const computed = Math.round(THUMB_HEIGHT * ratio);
     return Math.max(THUMB_MIN_WIDTH, Math.min(THUMB_MAX_WIDTH, computed));
 }
-function CaptureThumbnailStrip({ items, minPhotos, maxPhotos, backgroundColor = 'rgba(0,0,0,0.85)', textColor = '#ffffff', successColor = '#34C759', warningColor = '#FF9F0A', disablePreview = false, onItemPress, style, }) {
+function CaptureThumbnailStrip({ items, minPhotos, maxPhotos, backgroundColor = 'rgba(0,0,0,0.85)', textColor = '#ffffff', successColor = '#34C759', warningColor = '#FF9F0A', disablePreview = false, onItemPress, style, vertical = false, contentRotation, }) {
     // Built-in preview state — only used when the host hasn't
     // provided its own onItemPress handler.  Letting the host pass a
     // handler is how the AuditCaptureScreen unifies thumbnail
@@ -124,16 +124,19 @@ function CaptureThumbnailStrip({ items, minPhotos, maxPhotos, backgroundColor =
             ], accessibilityLabel: `Captured ${items.length} photos` }, text));
     }, [items.length, minPhotos, maxPhotos, successColor, warningColor]);
     return (react_1.default.createElement(react_native_1.View, { style: [styles.root, { backgroundColor }, style] },
-        react_1.default.createElement(react_native_1.FlatList, { data: items, horizontal: true, showsHorizontalScrollIndicator: false, keyExtractor: (item) => item.id, contentContainerStyle: styles.listContent, ListEmptyComponent: react_1.default.createElement(react_native_1.View, { style: [styles.placeholder, { borderColor: textColor }], accessibilityLabel: "No photos captured" },
+        react_1.default.createElement(react_native_1.FlatList, { data: items, horizontal: !vertical, showsHorizontalScrollIndicator: false, showsVerticalScrollIndicator: false, keyExtractor: (item) => item.id, contentContainerStyle: vertical ? styles.listContentVertical : styles.listContent, ListEmptyComponent: react_1.default.createElement(react_native_1.View, { style: [styles.placeholder, { borderColor: textColor }], accessibilityLabel: "No photos captured" },
                 react_1.default.createElement(react_native_1.Text, { style: [styles.placeholderText, { color: textColor }] }, "No photos")), renderItem: ({ item }) => (react_1.default.createElement(react_native_1.Pressable, { onPress: () => handleItemPress(item), disabled: disablePreview, accessibilityRole: "imagebutton", accessibilityLabel: "Open preview", 
                 // Resolve the width per-item — done at render rather than
                 // inside renderItem's style prop so the function isn't
                 // re-created on every parent render.
                 style: [
                     styles.thumbWrapper,
+                    // Spacing runs along the scroll axis: marginRight for the
+                    // horizontal strip, marginBottom for the vertical column.
+                    vertical ? styles.thumbWrapperVertical : styles.thumbWrapperHorizontal,
                     { width: thumbWidth(item), height: THUMB_HEIGHT },
                 ] },
-                react_1.default.createElement(react_native_1.Image, { source: { uri: item.uri }, style: styles.thumbImage, resizeMode: "cover" }))) }),
+                react_1.default.createElement(react_native_1.Image, { source: { uri: item.uri }, style: [styles.thumbImage, contentRotation], resizeMode: "cover" }))) }),
         countLine,
         react_1.default.createElement(CapturePreview_1.CapturePreview, { visible: previewItem !== null, imageUri: previewItem?.uri ?? '', imageWidth: previewItem?.width, imageHeight: previewItem?.height, onClose: closePreview })));
 }
@@ -145,12 +148,22 @@ const styles = react_native_1.StyleSheet.create({
         paddingHorizontal: 12,
         alignItems: 'center',
     },
+    listContentVertical: {
+        paddingVertical: 12,
+        alignItems: 'center',
+    },
     thumbWrapper: {
-        marginRight: 8,
         borderRadius: 4,
         overflow: 'hidden',
         backgroundColor: '#222',
     },
+    // Spacing applied along the scroll axis (see render site).
+    thumbWrapperHorizontal: {
+        marginRight: 8,
+    },
+    thumbWrapperVertical: {
+        marginBottom: 8,
+    },
     thumbImage: {
         width: '100%',
         height: '100%',

package/dist/camera/PanoramaBandOverlay.d.ts

@@ -115,5 +115,81 @@ export interface PanoramaBandOverlayProps {
      */
     captureOrientation?: BandCaptureOrientation;
 }
+/**
+ * Resolve band layout from capture orientation.  2026-05-18 (Issue #3)
+ * — uses the 4-way `BandCaptureOrientation` instead of the 2-way
+ * `state.isLandscape` so we can pick the right flex direction +
+ * arrow glyph in EACH landscape rotation.
+ *
+ * The two landscape rotations require different JS-coordinate setups
+ * because the phone tilts the JS coordinate system relative to the
+ * user differently:
+ *
+ *   LANDSCAPE-LEFT  (Apple: home indicator on user's RIGHT; phone
+ *                    rotated 90° CCW from portrait).
+ *     JS-left  = user-top
+ *     JS-right = user-bottom
+ *     Band at JS-bottom edge appears on user's RIGHT edge.
+ *     For "oldest at user-top, newest at user-bottom":
+ *       flexDirection = 'row' (array[0] at JS-left = user-top).
+ *     For arrow appearing as user-DOWN-arrow:
+ *       glyph `←` (rotated 90° CCW = points user-down).
+ *
+ *   LANDSCAPE-RIGHT (Apple: home indicator on user's LEFT; phone
+ *                    rotated 90° CW from portrait).
+ *     JS-left  = user-bottom
+ *     JS-right = user-top
+ *     Band at JS-TOP edge appears on user's RIGHT edge (so we move
+ *     the band to JS-top here, not JS-bottom).
+ *     For "oldest at user-top, newest at user-bottom":
+ *       flexDirection = 'row-reverse' (array[0] at JS-right = user-top).
+ *     For arrow appearing as user-DOWN-arrow:
+ *       glyph `→` (rotated 90° CW = points user-down).
+ *
+ *   PORTRAIT (and portrait-upside-down — collapsed because the band's
+ *             bottom-anchored position remains sensible either way):
+ *     Band at JS-bottom = user-bottom.  Row left-to-right.  Arrow `→`
+ *     reads as user-right-arrow (pointing along the horizontal pan
+ *     direction).
+ */
+/**
+ * v0.13.1 — pure rotation-decision helpers, extracted for unit testing
+ * (the lib's jest config is pure-TS, no component mounting; see
+ * jest.config.js).  These encode the orientation contract the band
+ * relies on, so a regression in the angles/branches is caught in CI
+ * rather than only on-device.
+ *
+ * `bandThumbRotation` — the CSS rotate transform that aligns a thumb's
+ * pixels with the band box.  Returns the transform array RN expects, or
+ * `undefined` for "no rotation".  Two regimes:
+ *   - vertical=false (portrait-locked UI): the box is device-aligned, so
+ *     a landscape device needs a 90° counter-rotation (CW for
+ *     landscape-left, CCW for landscape-right).
+ *   - vertical=true (non-locked, OS-rotated framebuffer): the screen
+ *     rotation already did half the work, so the compensation is the
+ *     OPPOSITE sign.
+ * Exported as `_bandThumbRotationForTests`.
+ */
+declare function bandThumbRotation(orientation: BandCaptureOrientation, vertical: boolean): Array<{
+    rotate: string;
+}> | undefined;
+/**
+ * v0.13.1 — the rotation actually applied to the per-keyframe (multi-
+ * thumb) TILES.  This is the EXIF double-rotation fix: the saved
+ * `keyframe-N.jpg` is sensor-native landscape + EXIF Orientation 6, which
+ * RN's <Image> already auto-rotates upright.  So in the portrait-locked
+ * (vertical=false) path NO further transform is applied — adding one
+ * double-rotates (the original v0.12 bug).  Only the non-locked
+ * (vertical=true) path needs the compensation.  Returns `undefined` for
+ * "no transform".  Exported as `_tileRotationForTests`.
+ */
+declare function tileRotation(orientation: BandCaptureOrientation, vertical: boolean): Array<{
+    rotate: string;
+}> | undefined;
+/** @internal test-only export — see `bandThumbRotation`. */
+export declare const _bandThumbRotationForTests: typeof bandThumbRotation;
+/** @internal test-only export — see `tileRotation`. */
+export declare const _tileRotationForTests: typeof tileRotation;
 export declare function PanoramaBandOverlay({ state, frameUris, captureOrientation, vertical, }: PanoramaBandOverlayProps): React.JSX.Element | null;
+export {};
 //# sourceMappingURL=PanoramaBandOverlay.d.ts.map

package/dist/camera/PanoramaBandOverlay.js

@@ -92,6 +92,7 @@ var __importStar = (this && this.__importStar) || (function () {
     };
 })();
 Object.defineProperty(exports, "__esModule", { value: true });
+exports._tileRotationForTests = exports._bandThumbRotationForTests = void 0;
 exports.PanoramaBandOverlay = PanoramaBandOverlay;
 const react_1 = __importStar(require("react"));
 const react_native_1 = require("react-native");
@@ -141,6 +142,55 @@ const MULTI_THUMB_HARD_CAP = 32; // safety net; host typically caps at 24
  *     reads as user-right-arrow (pointing along the horizontal pan
  *     direction).
  */
+/**
+ * v0.13.1 — pure rotation-decision helpers, extracted for unit testing
+ * (the lib's jest config is pure-TS, no component mounting; see
+ * jest.config.js).  These encode the orientation contract the band
+ * relies on, so a regression in the angles/branches is caught in CI
+ * rather than only on-device.
+ *
+ * `bandThumbRotation` — the CSS rotate transform that aligns a thumb's
+ * pixels with the band box.  Returns the transform array RN expects, or
+ * `undefined` for "no rotation".  Two regimes:
+ *   - vertical=false (portrait-locked UI): the box is device-aligned, so
+ *     a landscape device needs a 90° counter-rotation (CW for
+ *     landscape-left, CCW for landscape-right).
+ *   - vertical=true (non-locked, OS-rotated framebuffer): the screen
+ *     rotation already did half the work, so the compensation is the
+ *     OPPOSITE sign.
+ * Exported as `_bandThumbRotationForTests`.
+ */
+function bandThumbRotation(orientation, vertical) {
+    if (vertical) {
+        if (orientation === 'landscape-left')
+            return [{ rotate: '-90deg' }];
+        if (orientation === 'landscape-right')
+            return [{ rotate: '90deg' }];
+        return undefined;
+    }
+    if (orientation === 'landscape-left')
+        return [{ rotate: '90deg' }];
+    if (orientation === 'landscape-right')
+        return [{ rotate: '-90deg' }];
+    return undefined;
+}
+/**
+ * v0.13.1 — the rotation actually applied to the per-keyframe (multi-
+ * thumb) TILES.  This is the EXIF double-rotation fix: the saved
+ * `keyframe-N.jpg` is sensor-native landscape + EXIF Orientation 6, which
+ * RN's <Image> already auto-rotates upright.  So in the portrait-locked
+ * (vertical=false) path NO further transform is applied — adding one
+ * double-rotates (the original v0.12 bug).  Only the non-locked
+ * (vertical=true) path needs the compensation.  Returns `undefined` for
+ * "no transform".  Exported as `_tileRotationForTests`.
+ */
+function tileRotation(orientation, vertical) {
+    return vertical ? bandThumbRotation(orientation, vertical) : undefined;
+}
+/** @internal test-only export — see `bandThumbRotation`. */
+exports._bandThumbRotationForTests = bandThumbRotation;
+/** @internal test-only export — see `tileRotation`. */
+exports._tileRotationForTests = tileRotation;
 function layoutFor(orientation, vertical) {
     const commonInner = {
         alignItems: 'center',
@@ -326,42 +376,49 @@ function PanoramaBandOverlay({ state, frameUris, captureOrientation, vertical =
     // transform, so they appeared sideways in portrait-locked
     // landscape captures (the case the example app's batch-keyframe
     // engine hits).
-    const thumbRotationTransform = (0, react_1.useMemo)(() => {
-        // Empirical observation (on-device test 2026-05-28): captured
-        // per-keyframe JPEGs ARE saved in sensor-native landscape (not
-        // user-perspective), despite the cumulative panorama getting
-        // device-orientation rotation via finalize().  So:
-        //
-        //   jsPortrait box + landscape device: box is device-aligned;
-        //     image's "up" is at file-right (sensor convention).  Rotate
-        //     90° CW (landscape-left) / 90° CCW (landscape-right) to
-        //     align image up with box up.
-        //   jsLandscape box + landscape device: box is user-aligned via
-        //     OS screen rotation; image's "up" still at file-right.  To
-        //     align image up with box up, rotate the OPPOSITE direction
-        //     from the jsPortrait case — the screen-rotation already
-        //     handles half the work; we just need to compensate for the
-        //     remaining mismatch.
-        if (vertical) {
-            if (resolvedOrientation === 'landscape-left')
-                return [{ rotate: '-90deg' }];
-            if (resolvedOrientation === 'landscape-right')
-                return [{ rotate: '90deg' }];
-            return undefined;
-        }
-        if (resolvedOrientation === 'landscape-left')
-            return [{ rotate: '90deg' }];
-        if (resolvedOrientation === 'landscape-right')
-            return [{ rotate: '-90deg' }];
-        return undefined;
-    }, [resolvedOrientation, vertical]);
+    // Rotation for the single cumulative thumb (panorama-*.jpg, a JFIF
+    // with NO EXIF tag → RN does not auto-rotate it, so the transform is
+    // always needed).  See `bandThumbRotation` for the angle contract.
+    const thumbRotationTransform = (0, react_1.useMemo)(() => bandThumbRotation(resolvedOrientation, vertical), [resolvedOrientation, vertical]);
     const singleImageStyle = (0, react_1.useMemo)(() => thumbRotationTransform
         ? [react_native_1.StyleSheet.absoluteFill, { transform: thumbRotationTransform }]
         : react_native_1.StyleSheet.absoluteFill, [thumbRotationTransform]);
-    // Same rotation applied to the per-keyframe (multi-thumb) tiles.
-    const multiThumbStyle = (0, react_1.useMemo)(() => thumbRotationTransform
-        ? [styles.multiThumb, { transform: thumbRotationTransform }]
-        : styles.multiThumb, [thumbRotationTransform]);
+    // v0.13.1 — per-keyframe tile rotation is conditional on `vertical`.
+    //
+    // The keyframe JPEGs (`keyframe-N.jpg`) are saved as sensor-native
+    // landscape PIXELS *plus* an EXIF Orientation tag (= 6, "rotate 90°
+    // CW for display") — verified on-device: Android SM-A356U1 640×480
+    // + EXIF6, iOS iPhone16Pro 1920×1080 + EXIF6.  RN's <Image> (Fresco
+    // on Android, ImageIO on iOS) HONORS EXIF and auto-rotates each tile
+    // to gravity-upright on its own.  Whether a *further* JS transform is
+    // needed depends on the band box's coordinate frame:
+    //
+    //   vertical=false (portrait-locked UI): box is in portrait JS coords,
+    //     which align with the EXIF-upright tile → NO transform.  Applying
+    //     one here double-rotates (the original v0.12 bug — tiles appeared
+    //     90° off in portrait-locked landscape captures).  Verified fixed
+    //     on Android portrait-lock.
+    //   vertical=true (non-locked host, device-landscape): box is in
+    //     landscape JS coords, rotated 90° from the EXIF-upright tile →
+    //     the counter-rotation is STILL required (verified on iOS: with no
+    //     transform the tiles sit 90° off).
+    //
+    // So reuse `thumbRotationTransform` (which already encodes the correct
+    // per-orientation angle) ONLY in the vertical=true branch.
+    //
+    // The single cumulative thumb above always needs the transform: its
+    // source (`panorama-*.jpg`) is a JFIF with NO EXIF tag (verified:
+    // header ff d8 ff e0), so RN never auto-rotates it.
+    //
+    // Stitcher is unaffected — it reads `keyframe-N.jpg` with EXIF IGNORED
+    // (IMREAD_IGNORE_ORIENTATION) so it still gets the sensor-native
+    // pixels its pose intrinsics expect.  Display-only.
+    const multiThumbStyle = (0, react_1.useMemo)(() => {
+        const tileTransform = tileRotation(resolvedOrientation, vertical);
+        return tileTransform
+            ? [styles.multiThumb, { transform: tileTransform }]
+            : styles.multiThumb;
+    }, [resolvedOrientation, vertical]);
     return (react_1.default.createElement(react_native_1.View, { pointerEvents: "none", style: [styles.bandBase, layout.band] }, hasMultiThumb ? (
     // Multi-thumb path: one image per accepted keyframe, scrolling
     // horizontally (in JS-coords) within the band.  Content

package/dist/camera/PanoramaConfirmModal.js

@@ -44,7 +44,17 @@ function PanoramaConfirmModal({ visible, panoramaUri, width, height, onSave, onR
     // correctly inside a flexible container without us having to
     // measure the modal's available area on every layout change.
     const aspectRatio = width > 0 && height > 0 ? width / height : 16 / 9;
-    return (react_1.default.createElement(react_native_1.Modal, { visible: visible, animationType: "fade", transparent: true, statusBarTranslucent: true, onRequestClose: onDiscard },
+    return (react_1.default.createElement(react_native_1.Modal, { visible: visible, animationType: "fade", transparent: true, statusBarTranslucent: true, 
+        // v0.13.1 — RN's iOS <Modal> defaults to portrait-only.  Declare
+        // all four so the confirm modal stays aligned with the interface
+        // under a non-locked host.  Mirrors OrientationDriftModal +
+        // PanoramaSettingsModal (v0.12) and CapturePreview (v0.13.1).
+        supportedOrientations: [
+            'portrait',
+            'portrait-upside-down',
+            'landscape-left',
+            'landscape-right',
+        ], onRequestClose: onDiscard },
         react_1.default.createElement(react_native_1.View, { style: styles.backdrop },
             react_1.default.createElement(react_native_1.Text, { style: styles.title, accessibilityRole: "header" }, title),
             react_1.default.createElement(react_native_1.View, { style: styles.imageWrapper },

package/dist/camera/selectCaptureDevice.d.ts

@@ -0,0 +1,93 @@
+/**
+ * selectCaptureDevice — capability-aware back-camera selection.
+ *
+ * Replaces the single-physical-device request that caused two
+ * user-visible bugs (see docs/plans/2026-06-01-v0.13.2-multilens-
+ * device-selection.md):
+ *
+ *   1. 0.5× silently showed the wide-angle FOV on phones where the
+ *      ultra-wide is only exposed inside a multi-cam logical device —
+ *      vision-camera's single-lens filter mis-scored and fell back to
+ *      a plain wide-angle device.
+ *   2. flash threw `flash-not-available` on 0.5× because the standalone
+ *      ultra-wide device has no torch unit.
+ *
+ * Both stem from mounting ONE standalone physical device per lens.  The
+ * fix: prefer a MULTI-CAM device that carries the ultra-wide (so a
+ * single mounted device spans both FOVs via zoom AND carries the torch
+ * through its wide-angle member).  Fall back to standalone devices for
+ * phones — common on Android — where the ultra-wide has no multi-cam
+ * grouping, so we don't regress those.
+ *
+ * Pure + synchronous: takes a plain device list (the structural subset
+ * of vision-camera's `CameraDevice` we need) and returns the choice.
+ * No React, no vision-camera hooks — unit-tested directly.
+ */
+export type LensType = 'ultra-wide-angle-camera' | 'wide-angle-camera' | 'telephoto-camera';
+/**
+ * The structural subset of vision-camera's `CameraDevice` this selector
+ * reads.  Declared locally (not imported) so tests can build synthetic
+ * devices without the full vision-camera type, and so the SDK doesn't
+ * couple its selection logic to vision-camera's evolving shape.
+ */
+export interface DeviceLike {
+    id: string;
+    position: 'front' | 'back' | 'external';
+    physicalDevices: LensType[];
+    isMultiCam: boolean;
+    hasTorch: boolean;
+    minZoom: number;
+    neutralZoom: number;
+    maxZoom: number;
+}
+export type CaptureDeviceMode = 
+/** One multi-cam device spans wide + ultra-wide; switch lenses via zoom. */
+'multicam'
+/** Separate standalone wide + ultra-wide devices; switch by remounting. */
+ | 'standalone-uw'
+/** No ultra-wide anywhere; wide-angle only (no 0.5× chip). */
+ | 'wide-only';
+export interface CaptureDeviceSelection<D extends DeviceLike = DeviceLike> {
+    /** The device to mount for the `1×` lens (and for `multicam`, all lenses). */
+    device: D | null;
+    /**
+     * The device to mount when the user picks `0.5×` in `standalone-uw`
+     * mode (a separate physical ultra-wide).  Null in `multicam` (same
+     * device, zoom instead) and `wide-only` (no ultra-wide).
+     */
+    ultraWideDevice: D | null;
+    mode: CaptureDeviceMode;
+    /** Whether a 0.5× chooser should be offered at all. */
+    has0_5x: boolean;
+    /** Whether the `1×`/primary mounted device can flash (drives flash UI). */
+    hasTorch: boolean;
+}
+/**
+ * Choose the back-camera device(s) for capture.
+ *
+ * Priority:
+ *   1. multicam — a multi-cam device containing BOTH wide + ultra-wide
+ *      (best: one device, zoom-switch, torch via the wide member).
+ *   2. standalone-uw — a standalone wide AND a standalone ultra-wide
+ *      exist as separate devices (device-swap on lens change; flash
+ *      hidden on the torchless ultra-wide).
+ *   3. wide-only — no ultra-wide reachable; wide-angle only.
+ *
+ * @param devices  All enumerated camera devices (any position).
+ */
+export declare function selectCaptureDevice<D extends DeviceLike>(devices: readonly D[]): CaptureDeviceSelection<D>;
+/**
+ * Map a UI lens label to a vision-camera `zoom` value for the
+ * `multicam` mode (where lens switching is zoom, not device swap).
+ *
+ * - `1×`   → the device's `neutralZoom` (wide-angle baseline; vision-
+ *   camera docs: "where the camera is in wide-angle mode and hasn't
+ *   switched to ultra-wide or telephoto yet").
+ * - `0.5×` → `minZoom` (the ultra-wide end of the zoom range).
+ *
+ * Returns `neutralZoom` for any non-0.5× label as a safe default.
+ * Only meaningful in `multicam` mode; the standalone path swaps devices
+ * and ignores this.
+ */
+export declare function zoomForLens(device: Pick<DeviceLike, 'minZoom' | 'neutralZoom'>, lens: '1x' | '0.5x'): number;
+//# sourceMappingURL=selectCaptureDevice.d.ts.map