Repository navigation
Stage 2 walks the Android device the app was installed on (#179)
With a phone attached next to the emulator, the app was installed on the emulator (NATIVEAPPTEMPLATE_ADB_SERIAL, else an emulator-* serial) but the Stage 2 walk took the first Android device mobile-mcp listed, the phone, and failed on whatever app was open there. Without NATIVEAPPTEMPLATE_MOBILE_ANDROID_DEVICE, the walk now uses the same device as the install.
Verified against the templates' new releases
The 12-cell matrix (3 specs × 2 editions × 2 platforms, --visual=2) passed on 2026-10-29 against NativeAppTemplate-iOS 3.4.0, NativeAppTemplate-Android 3.4.0, NativeAppTemplate-Free-iOS 3.3.0 and NativeAppTemplate-Free-Android 3.3.0: Stage 2 46/46 on iOS and 48/48 on Android in every cell, about $0.21 per run. The clinic-queue cells also ran with --tests (Rails, iOS and Android suites green) on both editions.
docs/OUTPUT-CHECKLIST.md has checks for those releases: sign-in forms without errors on open, a deleted account's session back to the start, no stale offline error, invitation links that open the app, notifications asked on the first primary resource, light and dark appearance (#180).
Since 0.4.2 (no GitHub Release was made for these)
- 0.4.3: generated apps start at 1.0.0 (1) on iOS and Android, and leave the template's production credentials (
production.yml.enc) and Apple team (DEVELOPMENT_TEAM) behind. - 0.4.4: the rename leaves third-party identifiers alone (RevenueCat's
PurchasesAreCompletedBy, the Solid Queue / Cache / Cable schemas and migrations); the Stage 2 walk dismisses the dialogs that can cover the list while it waits for the Sample entry.
npx nativeapptemplate-agent@0.4.5 --help