This documentation is available as Markdown for AI agents and LLMs. See the full Markdown index or append .md to any documentation URL.

See which Android Emulator, iPhone, and iPad devices Expo Simulators can start, the default Android profile, and how to select a device.

Expo Simulators is a limited-access preview. It is not included with paid or free plans and is currently available only to select partners. Join the waitlist if you are interested in trying it.

Expo Simulators starts one virtual device for each session. On Android, it is an Android Emulator with a hardware profile. On iOS, it is an iOS Simulator device. Select the device with --device when the session starts. If you omit the flag, the runner uses medium_phone on Android and iPhone 17 on iOS.

Android Emulator profiles

Pass the profile ID to --device:

Every Android profile uses a 720 x 1600 screen at density 300. The profile selects the hardware definition of the device, not its screen size.

Android sessions use the system-images;android-35;google_apis;x86_64 system image, which is Android API level 35 with Google APIs. Install an APK that includes the x86_64 architecture.

iOS Simulator devices

Pass the device name or its unique device identifier (UDID) to --device:

iOS sessions use a macOS Tahoe 26.5 image with Xcode 26.6. Sessions on iPhone Duo use a different image with Xcode 27.1.

iPad devices

The iOS image also includes these iPad simulators:

• iPad (A16)
• iPad Air 11-inch (M4)
• iPad Air 13-inch (M4)
• iPad mini (A17 Pro)
• iPad Pro 11-inch (M5)
• iPad Pro 13-inch (M5)

The image also includes Apple Vision Pro and Apple TV simulators. The list can change, so list the devices in a session to get the exact names. To start an iPad, pass its exact name:

List the devices in a session

To see the devices that the remote runner offers, list them from a live agent-device session:

The list can change, so check it in each session. At start, only the session device is booted.

Use a second device in the same session

A session boots one device at start. In an iOS session, agent-device can boot and control another simulator. The default agent-device session is bound to the first device, so use a separate named session. Pass --session <name> and --device "<name>" to boot and open the second device. Then pass --session <name> on each later command for that device:

The boot can take about a minute. If you pass --device without --session, agent-device returns INVALID_ARGS because the default session is already bound to the first device.

The two --device flags work differently:

A UDID passed to the agent-device --device flag returns DEVICE_NOT_FOUND.

Resource classes

EAS CLI has a hidden, experimental --resource-class flag. It is not generally available. Do not use it in scripts.

Common questions