flutter run on iOS says Unable to boot the Simulator
Unable to boot the Simulator.Short answer
Check the simulator list first. If a device shows as unavailable or no runtime is installed, download the iOS platform. If the runtime exists, finish Xcode's first-launch setup and make sure xcode-select points at the Xcode you use. Quit all simulators before retrying.
Fix it fast
1Find out which cause you have
Run flutter doctor in verbose mode and print the selected Xcode path. The Xcode section shows a missing platform, license or command-line tools problem, which tells you which cause applies.
flutter doctor -v xcode-select -p2Match what you see, then jump to its fix
- 1
flutter doctor -v reports a missing iOS platform or no simulator runtime is available in XcodeThe iOS Simulator runtime is not installedFix - 2
Errors right after installing or updating XcodeXcode's first-launch setup was never finishedFix - 3
xcode-select -p prints an old or beta Xcode pathFlutter is pointed at a different Xcode than the one you updatedFix
- 1
What does the error look like?
Unable to boot the Simulator.
Cause 1 of 3
The iOS Simulator runtime is not installed
1Check
Xcode needs an iOS platform download to run any simulator. A new Xcode, or one updated recently, often starts without it.
flutter doctor -v2Fix
Download the iOS platform and its simulator runtime.
xcodebuild -downloadPlatform iOS3Verify
flutter doctor -v shows no Xcode issue and the simulator boots.
flutter doctor -v
open -a SimulatorConfirmed by docs.flutter.dev
Cause 2 of 3
Xcode's first-launch setup was never finished
1Check
Command-line tools need the Xcode path selected and the first-launch components installed, and the licenses accepted.
xcode-select -p
xcodebuild -version2Fix
Select your Xcode, run the first-launch step and accept the licenses.
sudo sh -c 'xcode-select -s /Applications/Xcode.app/Contents/Developer && xcodebuild -runFirstLaunch'
sudo xcodebuild -license3Verify
flutter doctor shows no Xcode issue and the simulator starts.
flutter doctor
open -a SimulatorConfirmed by docs.flutter.dev
Cause 3 of 3
Flutter is pointed at a different Xcode than the one you updated
1Check
Several Xcode copies on one Mac are common. Tools use whichever xcode-select names.
xcode-select -p
ls /Applications | grep -i xcode2Fix
Switch to the Xcode you want, and repeat the first-launch step for it.
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
sudo xcodebuild -runFirstLaunch3Verify
The path matches and flutter doctor is clean.
xcode-select -p
flutter doctor -vConfirmed by docs.flutter.dev
How do I stop it coming back?
- After each Xcode update, run the first-launch step and download the iOS platform if missing.
- Keep one Xcode in /Applications, or switch with xcode-select on purpose.
- Run flutter doctor after an Xcode or macOS update.
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?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
- Qist BazaarA buy-now-pay-later marketplace built from a blank repo, now past 100K downloads on Google Play.
Related fixes
Mobile apps
git, clang or xcrun stops working because the active developer folder is gone
xcrun: error: invalid active developer path (/Applications/Xcode.app/Contents/Developer), missing xcrun at: /Applications/Xcode.app/Contents/Developer/usr/bin/xcrun
The folder that xcode-select points to no longer holds developer tools, so xcrun, git, clang and make cannot start.
3 causes, each with a fixMobile apps
Apple rejected the app under Guideline 4.3, Design: Spam
Guideline 4.3(b) - Design - Spam
Guideline 4.3 is Apple's duplicate rule.
5 causes, each with a fixMobile apps
pod install cannot pick a version of a pod that satisfies every requirement
Specs satisfying the `FirebaseAuth (~> 11.0)` dependency were found, but they required a higher minimum deployment target.
CocoaPods tried every version of the named pod and none fit all requirements.
4 causes, each with a fixMobile apps
flutter run says: Could not run Runner.app, try Xcode Product > Run
Try launching Xcode and selecting "Product > Run" to fix the problem:
Flutter prints this when installing or launching the built app on the iPhone fails, and it hides the real reason.
4 causes, each with a fixMobile apps
flutter doctor says CocoaPods is installed but not working
You appear to have CocoaPods installed but it is not working.
Flutter runs pod --version and treats a failed or unreadable result as a broken install.
3 causes, each with a fixMobile apps
flutter run on iOS or macOS stops with Error running pod install
Warning: CocoaPods not installed. Skipping pod install.
Flutter only reports that pod install failed; the reason is in the lines just above it.
5 causes, each with a fix