mobile-e2e
Mobile E2E
Run the mobile Maestro tests for apps/mobile.
Files that matter
- Runner:
apps/mobile/e2e/run-maestro.sh - iOS auth flow:
apps/mobile/e2e/flows/ios/auth.yaml - Android auth flow:
apps/mobile/e2e/flows/android/core.yaml - Shared auth flows:
apps/mobile/e2e/flows/shared/*.yaml - Artifacts:
apps/mobile/e2e/artifacts/
Always do first
From repo root:
cd apps/mobile
pnpm run e2e:doctor
More from rssnext/folo
installing-mobile-preview-builds
Builds and installs the iOS preview build for apps/mobile using EAS local build and devicectl. Use when the user asks to install a preview/internal iOS build on a connected iPhone for production-like testing.
20update-deps
Update all dependencies across frontend and backend projects. Reads changelogs for breaking changes, checks affected code, runs tests, and provides a summary. Use when updating npm dependencies across the monorepo.
19mobile-self-test
Self-test a mobile feature change or bug fix after implementation in `apps/mobile`. Use this whenever the user asks to verify a mobile change, run simulator acceptance, smoke-test a mobile PR, or provide screenshot proof for a mobile fix. This skill decides between prod vs local API mode, starts the local follow-server when needed, builds a release app, uses Maestro only to bootstrap registration for non-auth work, then switches to screenshot-driven visual validation and returns screenshot evidence.
4desktop-release
Perform a regular desktop release from the dev branch. Gather changes since the last desktop tag, update the changelog, choose the desktop release mode in release-plan.json, bump the version, and prepare the release PR.
3mobile-release
Use when preparing a mobile release from the dev branch and deciding whether changes should ship through the app stores or through the OTA pipeline before creating the release PR to mobile-main.
3