macOS 27 Xcode Traps: Phantom 'Not Paired' Error and Simulator Crash from App Translocation
These two pitfalls waste hours because the visible error messages send developers toward re-pairing devices or reinstalling Xcode, when the actual fixes are a DDI source update and a quarantine attribute removal. On macOS 27, knowing these root causes turns a confusing failure into a five-minute repair.
On macOS 27, developers can run into two Xcode errors that point in the wrong direction. A real-device message saying the device must be paired persists even when pairing is fine, because the system's CoreDevice framework version 651.13.5 doesn't match the old DDI (CoreDevice-518.33) installed on the machine. The fix is to extract new DDI files from Xcode 27.1's XcodeSystemResources.pkg and run devicectl manage ddis update with flags that exclude the old sources.
Separately, the iOS Simulator crashes on launch with "Simulator cannot be opened" even after reinstalling Xcode. The crash log reveals AppTranslocation in the process path, a Gatekeeper mechanism that mounts quarantined apps to random read-only paths. Because Simulator.app relies on relative paths to find SimulatorKit.framework inside Xcode, the relocation breaks dyld lookup. Removing the com.apple.quarantine attribute on the top-level Xcode.app and Simulator.app fixes it.
The article also notes follow-up traps: cached preparation errors require quitting Xcode, and if the SDK doesn't support the device's iOS version, use the newer Xcode. For the simulator, a further issue is arm64-only runtimes with old fat libraries, solved by real-device debugging or adding arm64-simulator slices.
Both failures trace to macOS-level state being out of sync with Xcode's expectations, while the error messages stay at a high level and never mention the real component versions.
App Translocation is a general hazard for any nested app that relies on relative path lookups to external frameworks, not just Simulator.app; clearing the quarantine attribute before first launch avoids it.
Running multiple Xcode versions on one machine invites DDI drift because system directories like /Library/Developer/DeveloperDiskImages are shared, so one Xcode's CoreDevice can end up paired with another's older DDI.