Overview
Validate mobile builds from uploads, CI artifacts, and Expo EAS.
Autonomy mobile runs attach app-build evidence to the same review model used for web, API, and message checks. Use mobile docs when the journey starts from an iOS Simulator build, an Android APK or AAB, an Expo EAS output, or a CI handoff.
Supported platforms
- iOS — Simulator-target
.appbundle, packed as raw,.zip,.tgz, or.tar.gz. Runs execute on cloud iOS Simulators. - Android —
.apkor.aab. Runs execute on cloud Android emulators and launch the app by package name.
See Mobile Builds for the build commands and upload flow.
Artifact handoff
Mobile runs start from uploaded or CI-produced artifacts. Autonomy stores the artifact reference with the run so reviewers can connect the mobile session to the same evidence model used for web and API checks.
Supported paths
Use dashboard uploads for manual QA, local artifact uploads for smoke tests, CI artifact handoff for pull requests, and Expo EAS integration for managed Expo builds.
What evidence looks like
Mobile evidence includes the build artifact, device or simulator context, screenshots, native UI snapshots, logs, generated checks, and any linked API or message assertions. The run should make it clear which build was tested and which environment it communicated with.
Choosing a path
- Use dashboard upload when a human wants to validate a build quickly.
- Use local artifact upload when development produces the build outside CI.
- Use CI handoff when a pull request or release job builds the app.
- Use Expo EAS when Expo owns the build pipeline.