Xcode 27.1 Ships an iPhone Duo Simulator With Gaps

Apple released the Xcode 27.1 beta on Sept. 18, 2026, the first version to include a simulator runtime for iPhone Duo, the foldable device Apple has not yet shipped. Developers get five weeks with the simulator before the real hardware reaches anyone.

iPhone Duo starts at $1,999, with preorders opening Oct. 16 and the device shipping Oct. 23, according to 9to5Mac. That gives developers roughly five weeks between today's beta and launch day to find out whether their apps handle a folding display before customers do it for them, a shorter runway than Flet got when it reached 1.0 promising one Python codebase across six platforms with no new hardware shape to design around.

What the iPhone Duo Simulator still cannot do

Apple's own release notes list the runtime's gaps plainly, each tied to a bug number developers can file follow-ups against. StandBy, the lock-screen glanceable-info mode, is unavailable in the iPhone Duo Simulator runtime (187708663). Running and debugging most app extensions is unavailable in the same runtime (187708767). Apple also warns that the initial simulator launch can take several minutes (187708500), a wait that will run once per machine rather than once per project.

None of the four phones above run iPhone Duo's folding display, and that is the gap Xcode 27.1 is trying to close in software months before the hardware exists on a shelf next to them.

What breaks under Mac Catalyst

The beta's Mac Catalyst known issues are more disruptive than the simulator gaps, because they hit any project that targets iOS 27.1 at all, folding display or not. Projects using APIs specific to iOS 27.1 show compile errors under Mac Catalyst, errors like "undeclared identifier" and "has no member" (185924957). Apple's workaround is to wrap the affected code in #if !targetEnvironment(macCatalyst) in Swift or #if !TARGET_OS_MACCATALYST in Objective-C.

A second bug means projects that target iOS 27.1 show no Mac Catalyst run destination in Xcode at all (187046347); Apple's documented fix is to add a Mac Catalyst 27.0 minimum deployment target in project settings, a workaround rather than a patch.

Bug ID	Where	What breaks	Apple's workaround
185924957	Mac Catalyst	iOS 27.1 APIs fail to compile	Wrap in #if !targetEnvironment(macCatalyst)
187046347	Mac Catalyst	No run destination for iOS 27.1 targets	Add Mac Catalyst 27.0 minimum deployment
187708663	Simulator	StandBy unavailable on iPhone Duo runtime	None documented
187708767	Simulator	Most extensions unavailable on iPhone Duo runtime	None documented

What the notes do not say

The release notes give a fix for both Mac Catalyst bugs but list no workaround at all for the StandBy or extensions gaps, which means any app leaning on either has nothing to test against until a later beta closes them. That is a narrower known-issues list than Warpgate's 0.29.0 release, which fixed four advisories in a single update rather than leaving them open across beta cycles. Xcode 27.1 beta also requires a Mac running macOS Tahoe 26.6 or later to install, according to the same notes, so the five-week runway assumes a developer's host Mac is already current.

Apple's notes say the beta ships Swift 6.4 alongside SDKs for iOS 27.1, iPadOS 27, tvOS 27, watchOS 27, macOS 27 and visionOS 27, and that on-device debugging still reaches back as far as iOS 17. Apple has not said in these notes when the extensions or StandBy gaps close, only that Xcode 27.1 remains in beta.