Skip to main content
Run natural language flows against iOS and Android apps in the cloud. Use iOS Simulators and Android Emulators for fast coverage, or run the same flows on physical devices when you need real hardware.

​
Available devices and OS versions

Every mobile run can target a specific device model and OS version. In the run dialog, choose a Target, then select a Device and OS version. If you do not change the selection, Autosana uses the recommended latest combination. The device picker shows the exact model and OS combinations available for your app. iOS Simulator versions marked Fast launch use an optimized startup path; every listed combination is supported. For API runs, use List Devices to retrieve the current catalog, then pass one of the returned combinations in the run’s device object.

​
Physical Device Testing

Run any mobile flow on real hardware — actual iPhones, Pixels, and Galaxy devices — instead of an emulator or simulator. Same flows, same agent, real devices.

​
Build requirements

What you can run depends on the build you upload: For iOS, upload an .ipa built for physical devices. Android builds work on both targets with no changes.

​
Running on a real device

Click Run on a flow (or suite), set Target to Real device, and pick a device model and OS version. The picker lists the live device catalog — newest models first — and defaults to the newest available device.If your app’s active build is an .ipa, the dialog opens on Real device automatically.

​
Picking a device

The device object narrows which device the run lands on:
  • model — e.g. "iPhone 16 Pro", "Pixel 9", or "latest". Matches the names shown in the dashboard picker.
  • physical — use true for real hardware; it defaults to false.
  • os_version — "18" matches any 18.x; "18.3.1" matches only that version; "latest" keeps it rolling.
If no device matches your criteria, the run fails immediately with a clear error — pick a different model or OS version. Device availability is checked at run time; a model that’s momentarily busy is still attempted.

​
What you get

Real-device runs flow through the same pipeline as every other run:
  • Full video recording of the session, with per-action replay markers
  • Screenshots and annotations for every agent action
  • Device identity on the run page — the exact model and OS the run executed on (e.g. Pixel 9 · Android 16 · Real device)
  • Suites share one device session across their flows, so back-to-back flows start fast
Real-device runs take ~1–2 minutes longer to start than emulator runs while a device is acquired, and iOS sessions take a few extra minutes to finalize their video after the run completes.

​
Native in-app purchases

Testing native Apple or Google purchase flows on private devices requires an enterprise contract with Autosana and coordinated onboarding. Contact us before preparing a build so we can confirm feasibility, device availability, and the signing and test-account setup. Selecting Real device alone does not configure native purchase testing. See Testing In-App Purchases for onboarding details and the self-service RevenueCat Test Store workflow.

​
Push notifications

End-to-end push-notification testing on physical iOS and Android devices uses private devices that preserve the app’s original signing and notification entitlements. This requires an enterprise contract. Contact us for availability and setup. For self-service APNs and FCM testing, see Testing Push Notifications for the iOS Simulator and Android Emulator workflow.