When an iPhone disappears from Xcode’s destination menu, check the installed iOS simulator runtime first. An iPhone device type and an iOS runtime are separate pieces. A device choice is only useful when its runtime is available to the Xcode installation doing the build.
Use the symptom to pick the check
The iOS version is missing
Open Xcode Settings → Components and install the runtime you need, if that runtime is available for your version of Xcode.
The runtime exists but the device is missing
Check Window → Devices and Simulators. Create a simulator using an available device type and the intended runtime.
Xcode sees it but Terminal does not
Compare the Xcode app you opened with xcode-select -p. If you keep multiple versions installed, the command line may be pointing at a different developer directory.
To confirm the fix, run xcrun simctl list devices available and match the exact destination used by your project. On a hosted runner, confirm the runtime is installed on the runner too.
Apple’s guide to installing Xcode components
A concrete example: the iOS version exists, but the test still cannot start
Suppose the workflow asks for a specific iPhone model and iOS version. You can see the iOS runtime in Xcode, but xcrun simctl list devices available shows no matching device. Open Devices and Simulators, create a device using that runtime, and run the list command again. If the device appears, test the same destination your workflow uses. On a shared Mac with several similarly named simulators, a device ID can remove ambiguity for that machine. Avoid committing one Mac’s device ID into a workflow that runs on other machines.
Separate a missing simulator from an incompatible destination
Run xcodebuild -showdestinations -scheme YOUR_SCHEME from the project directory, replacing YOUR_SCHEME with your actual scheme. If your build normally uses a workspace, pass the same workspace option here. Compare that output with the devices listed by simctl. A simulator listed by simctl may still be unsuitable for the chosen scheme. Review the target platform and deployment settings if the scheme excludes the destination.
After the fix, run the same build or test command that failed. Seeing a device in the menu is a useful checkpoint. A successful run with the intended destination is the stronger check.