Getting Legacy iOS Apps Bootable on the iPhone Duo Simulator in Xcode 27.1
Apple will ship more arm64-only simulator devices, and each new one re-triggers the same three failure modes: excluded architectures, device-only SDK slices, and hidden run destinations. This Podfile switch plus stub-library pattern keeps a simulator package running the UI without waiting for SDK vendors, with the clear caveat that true verification still requires a device.
The Xcode 27.1 iPhone Duo simulator runtime ships arm64 only, with no x86_64 slices. Legacy iOS projects fail on it for three stacked reasons: their simulator builds exclude arm64 via an EXCLUDED_ARCHS setting inherited from the x86_64 era, some audio/video, sharing, and crash-reporting SDKs ship only device slices, and the arm64-only runtime hides Duo from the destination list entirely until that exclusion is lifted.
The migration path handles each stage in order. Verify the runtime is arm64-only with simctl and lipo on dyld_sim, then strip the arm64 exclusion from simulator xcconfig files through a CocoaPods post_install hook so generated files do not get overwritten. Each dependency failure needs separate diagnosis: Swift module directories reveal missing simulator interfaces, vtool platform markers (IOS vs IOSSIMULATOR) decide link-stage ownership, and otool segment tables catch corrupt slices. The fix runs through a SIM_BUILD environment switch in the Podfile that swaps device-only SDK pods for local same-named stub libraries.
Call-site handling proceeds from fewest to most references: `#if !TARGET_OS_SIMULATOR` guards for light usage, a same-named stub library with identical headers and empty implementations for heavy usage. Stubs must log unimplemented selectors via `doesNotRecognizeSelector:` and implement every method that returns a value, because empty implementations pass linking but crash at runtime. Acceptance requires the simulator app to boot and navigate all main pages, the device build to remain unchanged, and the dependency lock file to stay untouched.
The arm64-only simulator runtime does not just change which architectures compile; it changes which devices even appear in the destination list. An architecture exclusion setting can hide hardware entirely, making the problem look like a project configuration issue rather than a runtime reality.
The stub-library approach is a deliberate trade of functionality for progress: its contract is "don't crash, not don't work." Teams that fail to distinguish crashes from unresponsive features will chase phantom faults during adaptation.
The advice to verify with real builds rather than empty projects is a warning about false positives: static linking only pulls in referenced symbols, so a link test in a toy project proves nothing about a real one.
The author is honest about scope: simulator verification is "approximate," and no performance, account chains, or core system capabilities can be confirmed without a device. The workflow buys UI and interaction progress but never replaces a device test pass.