Expo says 'No iOS devices available in Simulator.app', or the app never opens in the iOS Simulator
CommandError: No iOS devices available in Simulator.appShort answer
Expo CLI can only open the app in a simulator that Xcode already knows. Run xcrun simctl list devices available first. An empty list means no iOS runtime is installed. A list with devices means boot one, select the right command line tools and accept the licence, or answer the first-run prompt to open Expo Go.
Fix it fast
1Find out which cause you have
Ask Xcode which simulators it can use. An empty list points to the first cause; a list with devices points to the others.
xcrun simctl list devices available2Match what you see, then jump to its fix
- 1
The command from the first step prints no iPhone devices at allNo iOS simulator runtime is installedFix - 2
The device list has entries, yet Expo CLI finds no running simulatorDevices exist, but none is booted and the Simulator app is not openFix - 3
Expo prints an Xcode licence warning, or other xcrun and xcodebuild commands fail in the same terminalThe command line tools are not selected, or the Xcode licence is not acceptedFix - 4
The simulator is booted and Expo says it is opening the project, yet the app does not appear, on the first runThe simulator is open, but the first Expo Go prompt is still waitingFix
- 1
What does the error look like?
CommandError: No iOS devices available in Simulator.app
Cause 1 of 4
No iOS simulator runtime is installed
1Check
A simulator needs an iOS runtime, which Xcode installs separately from the app itself. Open Xcode, then Settings and Components, and look under Platform Support for iOS.
xcrun simctl list runtimes2Fix
In Xcode choose Settings, Components, then Get next to the iOS entry under Platform Support, and wait for the download to finish.
# Xcode > Settings > Components > Platform Support > iOS > Get3Verify
The listing now shows iPhone devices.
xcrun simctl list devices availableConfirmed by docs.expo.dev
Cause 2 of 4
Devices exist, but none is booted and the Simulator app is not open
1Check
Expo CLI targets the simulator that was opened most recently. If none is running, it has nothing to pick, and the app named Simulator may simply never have been started. In Xcode 27 that app is called DeviceHub.
xcrun simctl list devices booted2Fix
Boot a device by name from your list, then open the simulator app that belongs to your Xcode version, and press i again in the Expo terminal. Shift and I lets you choose a device from a list.
xcrun simctl boot "iPhone 17"
open -a Simulator # Xcode 26
open -a DeviceHub # Xcode 273Verify
The booted list shows the device and the simulator window is visible.
xcrun simctl list devices bootedConfirmed by docs.expo.dev
Cause 3 of 4
The command line tools are not selected, or the Xcode licence is not accepted
1Check
Expo's setup expects the newest command line tools to be selected in Xcode. If Xcode warns about its licence, do what the warning says before you try again.
xcode-select -p2Fix
In Xcode open Settings, then Locations, and choose the newest version in the Command Line Tools menu. If a licence warning appeared, run the exact command it suggests and try again.
# Xcode > Settings > Locations > Command Line Tools: pick the newest version3Verify
xcode-select -p prints a path inside the Xcode app, and pressing i in the Expo terminal starts the simulator.
xcode-select -p
npx expo startConfirmed by docs.expo.dev
Cause 4 of 4
The simulator is open, but the first Expo Go prompt is still waiting
1Check
On the first install, iOS shows a prompt to open Expo Go. It needs a tap in the simulator window before the app can start.
# look at the simulator window for a dialog about opening Expo Go2Fix
Click into the simulator and press OK on the prompt.
# simulator: tap OK on the dialog3Verify
Expo Go opens and loads the project; the next press of i does it without the prompt.
npx expo startConfirmed by docs.expo.dev
How do I stop it coming back?
- After each Xcode update, run xcrun simctl list devices available once and install the iOS runtime if the list is empty.
- Name the simulator you want in your team's setup notes, and boot it before starting Expo.
- Keep the Command Line Tools selection in Xcode Settings on the same Xcode you build with.
- Open the simulator once and answer its first prompts before a demo or a deadline.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Related fixes
Mobile apps
react-native run-ios cannot find the iPhone simulator
Could not find iPhone X simulator
run-ios starts a default simulator by name.
2 causes, each with a fixMobile apps
An older iOS simulator runtime does not show up in Xcode 26
The simulator you need is not in the run destination menu
A new Xcode installs only the newest simulator runtime for each platform.
2 causes, each with a fixMobile apps
Xcode will not download or install an iOS Simulator runtime
Could not download and install iOS Simulator runtime
When the Platforms download in Xcode fails, skip the interface.
3 causes, each with a fixMobile apps
flutter run on iOS says Unable to boot the Simulator
Unable to boot the Simulator.
Check the simulator list first.
3 causes, each with a fixMobile apps
Cannot change the App Privacy answers in App Store Connect
Publish Your App Privacy Responses?
Only the Account Holder, Admin and App Manager roles can answer the App Privacy questions.
2 causes, each with a fixMobile apps
App record creation fails because you lack permission
You cannot add a new app in App Store Connect as a Developer or limited user
Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.
3 causes, each with a fix