> Xcode 27.1 Beta or Xcode 27.2 Beta: Which One Do You Need?

Normally the Xcode beta story is simple: there's one beta, you install it, and you move on. This month is different. Apple shipped Xcode 27.2 beta on September 16, then Xcode 27.1 beta two days later, and the two aren't a sequence where the newer one replaces the older. They cover different things, and depending on what you're working on, you may need one, the other, or both.

What Each Beta Is For

Xcode 27.1 beta exists for iPhone Duo. Apple's September 16 developer update explained that iPhone Duo will run iOS 27.1 when it becomes available on October 23, and that Xcode 27.1 adds development support for it: updated SDKs and a simulator that supports the device's poses and orientations. The Xcode 27.1 beta release notes list SDKs for iOS 27.1 and the 27 versions of Apple's other platforms.

Xcode 27.2 beta is the regular next-release beta. Its release notes list 27.2 SDKs for every platform, and they open with a note telling you to download Xcode 27.1 beta to get the iOS SDK and simulator support for iPhone Duo. The 27.2 SDKs bring their own changes, like the expanded App Tracking Transparency prompt for the EU and leading-aligned navigation titles in UIKit, and the OS 27.2 beta 2 releases followed on September 21.

Some things are shared. Both betas include Swift 6.4, both require a Mac running macOS Tahoe 26.6 or later, and both support on-device debugging for iOS 17 and later, tvOS 17 and later, watchOS 10 and later, and visionOS.

So the short answer: if you're getting ready for iPhone Duo, you need 27.1. If you want to adopt 27.2 APIs or try the new tooling, you need 27.2. If you're doing both, install both.

Working With Xcode 27.1 Beta

Beyond the SDK, 27.1 adds one Duo-specific Previews feature: the canvas overrides picker has a new Display group for previewing content on a device's alternative display. It's handy for checking how a view looks on the outer display without launching anything.

The release notes also list some Simulator known issues worth knowing before you lose an afternoon to them. The initial Simulator launch can take several minutes. StandBy isn't available in the iPhone Duo runtime, and neither is running or debugging most app extensions, so widget and extension work still needs another simulator for now.

The bigger surprise is Mac Catalyst. If your project also builds for Mac Catalyst, code that uses iOS 27.1 APIs can fail to compile for Catalyst with the usual "undeclared identifier" or "has no member" errors. Apple's workaround is to wrap that code in #if !targetEnvironment(macCatalyst) so the Catalyst build skips it. A related issue is that projects targeting iOS 27.1 show no Mac Catalyst run destination at all. The fix there is to add a Mac Catalyst minimum deployment of 27.0 in your target settings.

Working With Xcode 27.2 Beta

The headline tooling change in 27.2 is the JSON-based project format, which stores your project configuration as a readable .xcproj file instead of project.pbxproj. I covered the switch in the article on the new project format. One detail from the release notes matters when you're juggling two betas: projects using .xcproj also open in earlier versions of Xcode 27. Converting a project in 27.2 doesn't lock out a teammate who's working in 27.1.

There are a few known issues. If you've also installed the macOS 27.2 beta, Xcode can crash during code completion. Apple's workaround turns off enhanced code completion ranking with a preference:

defaults write com.apple.dt.Xcode CodeCompletionAssetsToLoad /dev/null

Once a later beta fixes the crash, you can remove the override with defaults delete com.apple.dt.Xcode CodeCompletionAssetsToLoad.

The macOS, watchOS, tvOS, and visionOS SDKs in 27.2 also incorrectly report 27.1 as a valid deployment target. Apple warns that builds may behave unexpectedly if you pick it, so leave those platforms at 27.0 or 27.2. The same note mentions that Mac Catalyst builds with a 27.1 or 27.2 deployment target may not be able to use newly introduced API.

Device Hub has a couple of rough edges in 27.2 too. Keyboard and mouse input isn't accepted by simulators running OS versions before iOS 18, tvOS 18, watchOS 11, and visionOS 2. And after you disconnect a physical device that had Simulate Hardware Keyboard turned on, the device can stay in hardware keyboard mode for up to two minutes, which means the software keyboard won't appear when you tap a text field. Waiting it out is the only workaround.

Keeping Both Installed

Nothing stops you from having Xcode 27, 27.1 beta, and 27.2 beta on the same Mac. Beta downloads typically unpack with the same default app name, so rename each one as soon as it's extracted, something like Xcode-27.1-beta.app and Xcode-27.2-beta.app. That also keeps the version visible in Spotlight and the Dock.

The GUI is easy since you just open the Xcode you want. The command line needs more care, because xcodebuild, xcrun, and anything else in your scripts use whichever Xcode is currently selected:

# Which Xcode do the command line tools use right now?
xcode-select -p
xcodebuild -version

# Change the default for every terminal and script
sudo xcode-select -s /Applications/Xcode-27.1-beta.app

# Or pick an Xcode for a single command without changing the default
DEVELOPER_DIR=/Applications/Xcode-27.2-beta.app/Contents/Developer xcodebuild -version

The DEVELOPER_DIR approach is the safer habit when you switch often. It scopes the choice to one command, so a forgotten xcode-select can't quietly send tomorrow's release build through a beta toolchain. If you install Xcode versions often, a tool like xcodes can handle the downloading, naming, and switching for you.

Which Xcode Ships Your App

Betas are for testing. The App Store Connect release notes say builds from Xcode 27.2 beta (as of September 16) and Xcode 27.1 beta (as of September 18) can be submitted for internal and external TestFlight testing. The September 14 entry for Xcode 27, by contrast, covers uploads for the App Store as well as TestFlight. So your production builds still come from the released Xcode 27, and the betas feed TestFlight.

That gives most teams a clear setup for the next few weeks: Xcode 27 for anything that ships, Xcode 27.1 beta for iPhone Duo layout and camera work, and Xcode 27.2 beta when you want to try the 27.2 SDKs or the new project format. Check xcodebuild -version before you archive, and if you're starting on the Duo side, how to get your app ready for iPhone Duo covers what to test once the simulator is running.