E2E

Verify TrueSheet's behavior on the iOS simulator, the Android emulator, and mobile web with evidence, not eyeballing. Every claim — "fixed", "regression", "pre-existing" — should come with a frame trace, an event log, a debug log line, a viewport readout, or an A/B result against HEAD.

Read argent-device-interact before driving a device.

When to use

• A change in ios/, android/, or the web sheet (src/web, *.web.tsx) needs to be exercised on a device or browser, or reviewed for regressions.
• Something visibly misbehaves: a sheet, footer, or dim jumps, flickers, or lands at the wrong height.
• Event or timing correctness: onPositionChange realtime vs settled, detent changes, props applied (or lost) around present, dismiss, cancelled swipes, or stacked sheets.
• A timing-dependent race or crash needs a deterministic repro.
• Web keyboard or visual-viewport behavior in mobile Safari or Chrome.
• A bug report needs classifying as a regression or pre-existing by comparing against HEAD.

1. Build, install, launch

Native: bare example (example/bare), iOS bundle id and Android package are both truesheet.example (Android activity .MainActivity). Native library changes need a rebuild; JS changes hot-reload through Metro.