Xcode 27.2 RC Can't Find Simulators? 2026 Beginner Checks

The Xcode 27.2 RC run destination list is empty, or the iPhone simulator you need is missing.

Fastest fix: First check whether the required simulator platform is installed, then check whether a compatible device is available and selected, and only then inspect the project target. Do not reinstall Xcode just because the list looks incomplete.

Who this is for: Students whose course requires Xcode 27.2 RC and whose run destination list does not show the expected simulator.
Windows learners considering access to a Mac can use the checks below to confirm the environment before starting coursework.
Anyone trying a release candidate can check its status and platform support before changing a course project.

Last updated: October 30, 2026. The Apple release record supplied for this guide lists Xcode 27.2 RC with a publication date of October 19, 2026. Release-candidate status can change, so check the Apple Developer release record and the Xcode 27.2 RC release notes before relying on that status.

Start by identifying what “missing” means

“Simulator missing” can describe different problems. The distinction matters because each one needs a different check.

• No simulator devices appear in the run destination list. The list may have no available device that matches the current project, or the relevant platform support may not be present.
• The list appears, but the expected device is absent. Check whether a compatible simulator device is available and whether the project is targeting the platform expected by the course.
• A simulator can be selected, but it will not start. That is a launch problem, not the same as a missing device.
• The simulator opens, but the app will not build or run. That points toward the project, its build settings, or its compatibility with the selected destination.

Apple describes how to choose a simulated or physical run destination in its guide to running an app on simulated or physical devices. That distinction is useful here: a simulator device is a destination for running an app, not proof that the project itself is configured correctly.

Before changing anything, record the exact screen and visible message. Note whether the problem is in the run destination list, the simulator window, or the build output. If the course provides a required Xcode version, platform, or device type, keep that information beside the error. It will help separate an environment mismatch from a project problem.

Check that the required platform support is available

A simulator device and its platform support are related, but they are not interchangeable. A device list cannot offer a destination that the installed Xcode environment does not support. Equally, seeing a platform component does not prove that the specific simulator model needed by a course is available.

Start with the version installed on the Mac. Check the Xcode version and build identifier through Xcode itself or the command-line tools. Apple’s Xcode command-line tools reference documents the relevant tools. For a simple record, use:

xcodebuild -version

The output identifies the Xcode version and build version. Save both, rather than recording only “Xcode 27.2 RC.” If the course support request later asks which build was used, the build identifier can help distinguish installations.

Next, compare the installed release with the course requirement and Apple’s Xcode system requirements. The required macOS version is part of the check. If the Mac cannot run the required Xcode release, changing simulator devices will not solve that underlying compatibility issue.

Then inspect the components offered by the installed Xcode version. Apple’s guide to downloading and installing additional Xcode components explains the official process. Follow the instructions that apply to the installed release, and confirm what is actually available in its settings or download options. Do not rely on a menu label copied from an older tutorial; labels and available components can vary by Xcode release.

If the component is absent, stop before changing project settings. Check Apple’s release notes for the relevant version and confirm whether that platform is supported there. The official Xcode 27.2 RC notes are the appropriate source for release-specific details. If the course requires a platform that the installed version does not offer, ask the course provider which supported Xcode and platform combination to use.

A missing destination is evidence that something needs checking, not evidence that Xcode is corrupt. Confirm the platform and version before deciding to reinstall.

Separate the device list from the project target

Once the platform support is confirmed, inspect the run destination and project separately. These checks can look similar to a beginner, but they answer different questions.

First, look for the expected simulator in the available run destinations. If another simulator is listed, note its platform and device name. Do not select a different destination just to make the list stop looking empty; it must match the project and the course instructions.

If no suitable device appears, check whether the required simulator device is available in the installed environment. Apple’s documentation on adding additional simulators explains the official way to add simulator devices. Use that documentation to verify the options available for the installed Xcode version. Avoid assuming that a particular model or runtime will always be offered.

Then inspect the project’s supported run destination. Apple’s guide to creating an Xcode project for an app covers how an app project is set up. For an existing course project, compare its platform and deployment settings with the course instructions. A project configured for a different platform cannot be made suitable merely by changing the simulator selection.

Use the visible evidence to sort the result:

• Platform support is absent: verify Xcode and its components against Apple’s release documentation.
• Platform support is present, but the device is absent: check available simulator devices and whether the required device can be added.
• The device is present, but not selected: choose the course-compatible run destination.
• The simulator is selected, but the app cannot build: preserve the build error and check project settings and course compatibility.

This avoids treating every symptom as a single “simulator bug.” It also gives a course instructor or support person a useful report: the Xcode build, the selected destination, and the point where the process stops.

When the simulator appears but does not solve the exercise

A visible device is a good sign, but it is not a complete pass. The next question is whether the course project can use that destination.

If the simulator opens but the app fails to build, record the complete build message and the selected destination. Check the course’s required project files and any specified Xcode version before editing settings. A build failure can occur even when the simulator platform and device list are working normally.

If the simulator launches but the app does not reach the course’s expected screen, note which step completed: project opened, destination selected, build started, app launched, or exercise verification reached. This keeps the report precise. “The simulator is missing” is not accurate if the device appears and the failure occurs only after the project begins building.

For an Xcode 27.2 RC-specific issue, consult the release notes before attributing the problem to the release candidate. Apple’s release notes are the source for documented changes and known issues. If the notes do not describe the observed behavior, report it as unconfirmed rather than treating a guess from a forum or an old tutorial as established fact.

When asking for help, include the course’s required Xcode and platform, the installed Xcode version and build, the selected run destination, and the exact visible message. Avoid posting project secrets or personal data in screenshots. A focused report makes it easier to tell whether the next step belongs to the environment, the simulator, or the course project.

Common questions before changing the setup

Why is the iPhone simulator missing from Xcode 27.2 RC?

Check platform support first, then check the available devices and project destination. An empty list does not identify the cause by itself. The course may require a platform component that is not installed, a device that is not available in the current setup, or a project target that does not match the expected platform. Verify each against Apple’s current documentation and the course instructions before reinstalling.

Does Xcode need a separate simulator platform download?

Some components can be installed separately, so the installed Xcode may not already include every component a course needs. Use Apple’s additional-component instructions and check the options shown by that version of Xcode. Do not assume a tutorial written for another release describes the current interface or available downloads. Confirm the component is present before troubleshooting the project.

Is an empty simulator list a project-settings problem?

It might be, but that is only one possibility. A missing platform component or unavailable simulator device can produce a similar symptom. Check whether the platform is supported and the device is available before changing project settings. If a compatible destination is listed but the app fails to build, then investigate the project target and build output as a separate issue.

Can a student check the course simulator without owning a Mac?

A student can check a remote Mac environment before committing to coursework, but should verify the actual Xcode and macOS versions, the required platform component, the access method, and whether the course project can select the expected simulator. Do not infer those details from a general service description. Confirm the current environment information and test the course’s own task before depending on it.

Verify the course task before switching environments

Before continuing on the same Mac or trying another one, run a small course-relevant check. The aim is not to complete the assignment; it is to find out whether the required destination and project path are available.

Use this sequence:

• Compare the course’s stated Xcode version and platform with the installed versions.
• Confirm that the required platform support is offered and installed.
• Check that the expected simulator device appears as a selectable run destination.
• Open the course project and verify that its target matches the instructions.
• Try the first course step that should build or launch the app.
• Record the Xcode version, build, macOS version, selected destination, and any complete error text.

For a compact record, use a note like this:

Course-required Xcode:
Installed Xcode and build:
macOS version:
Required platform support:
Expected simulator:
Visible run destination:
First step that fails:
Exact message:

The Xcode release record identifies Xcode 27.2 RC and its October 19, 2026 publication date, but it does not make that release the right choice for every class. Check whether Apple’s page still lists it as a release candidate or whether a later release has replaced it. Then follow the course’s stated requirements; do not silently switch versions when the assignment depends on a particular environment.

If there is no local Mac, first compare the course requirements with the current environment information. The RunAMac location listings and RunAMac Help Center can help confirm what information is available before choosing an environment. If a listed Mac option is under consideration, inspect its current details, such as the RunAMac Mac mini Japan page, rather than assuming it includes a particular Xcode release or platform component.

A Windows-only setup can be useful for learning concepts and editing code, but it cannot substitute for checking an actual macOS and Xcode environment when a course specifically requires an iOS simulator. Buying a Mac gives local access, but it may not make sense for a short course or a temporary compatibility check. A remote Mac can avoid that upfront purchase, while adding remote-access dependence and requiring a careful check of the offered software and course workflow.

When the list is still empty, keep the diagnosis narrow: confirm platform support, verify the device, then inspect the project. For a temporary course or a test of the required environment, RunAMac may be worth considering after those requirements are clear. Review the available environment details first, and use a short course-task check to confirm that the required simulator is actually usable.

Frequently asked questions