An older iOS simulator runtime does not show up in Xcode 26
No simulators for the iOS version you need in the run destination menuShort answer
A new Xcode installs only the newest simulator runtime for each platform. Older iOS versions must be added by hand. Open Xcode > Settings > Components, use Add Platforms under Other Installed Platforms, or download one with xcodebuild -downloadPlatform and -buildVersion.
Fix it fast
1Find out which cause you have
See which runtimes this Xcode can use right now.
xcrun simctl list runtimes2Match what you see, then jump to its fix
What does the error look like?
No simulators for the iOS version you need in the run destination menuThe simulator you need is not in the run destination menu
Cause 1 of 2
The older runtime was never installed
1Check
Components settings shows Platform Support, Other Components and Other Installed Platforms. Earlier simulator runtimes appear under the last one only after you add them.
xcodebuild -showsdks2Fix
In Xcode > Settings > Components, click Add Platforms under Other Installed Platforms, filter to iOS, pick the version and click Download & Install.
# command line version, with an example OS version:
xcodebuild -downloadPlatform iOS -buildVersion 18.03Verify
The runtime shows in the list and in the run destination menu.
xcrun simctl list runtimes | grep -i iosConfirmed by developer.apple.com
Cause 2 of 2
A downloaded runtime image was not imported, or the system components are missing
1Check
A downloaded runtime must be imported on each Mac. Apple's order is: select the Xcode, run first launch to install system components such as simctl, then import the image.
xcode-select -p
ls ~/Downloads/*.dmg2Fix
Select the Xcode you use, run first launch, then import the runtime image.
xcode-select -s /Applications/Xcode.app
xcodebuild -runFirstLaunch
xcodebuild -importPlatform "~/Downloads/iOS 18.0 Simulator Runtime.dmg"3Verify
simctl lists the imported runtime.
xcrun simctl list runtimesConfirmed by developer.apple.com
How do I stop it coming back?
- After each Xcode update, re-check Components for the runtimes your support policy needs.
- Download runtimes once with -exportPath and import them on other Macs instead of fetching each time.
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
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 fixMobile apps
You cannot find the button to pull your app back from review
No 'remove this version from review' message appears on the version page
There is no button called Reject Binary.
3 causes, each with a fixMobile apps
Your Apple Account cannot sign in to App Store Connect
Sign-in to App Store Connect is refused for an account that should have access
App Store Connect does not open to every Apple Account.
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
App Store Connect rejects a screenshot because it has transparency
Images can't include alpha channels or transparencies.
App Store Connect does not accept screenshots that carry an alpha channel or transparent pixels.
2 causes, each with a fix