Xcode 27.2 is out: what got fixed, what is still open
Xcode 27.2 is out, and its headline is Device Hub: it now passes touch input to a device, supports StandBy on iPhone Duo and adds a few simulator tools. It also leaves one 27.1 build error open and brings two new known issues, so the update comes with a short list of things to check.
In short
- Device Hub gets the biggest set of changes: touch from Sidecar, StandBy on iPhone Duo, and simulator shake, fall and memory pressure.
- A few 27.1 problems are closed (the camera accessory issue and two Interface Builder bugs). The Mac Catalyst build error is not.
- Two known issues are new: four platform SDKs report 27.1 as a valid deployment target, and cloning a 27.2 simulator can fail.
- App Store Connect accepts apps built with Xcode 27.2 for the App Store and TestFlight.
| Xcode 27.1 | Xcode 27.2 | |
|---|---|---|
| Release date | October 15, 2026 | October 29, 2026 |
| Build | 27A9275 | 27B52 |
| SDKs | iOS 27.1, the rest 27 | 27.2 for iOS, iPadOS, tvOS, watchOS, visionOS and macOS |
| Swift | 6.4 | 6.4 |
| Needs | macOS Tahoe 26.6 | macOS Tahoe 26.6 |
| App Store Connect builds | accepted from release day | accepted from October 30 (RC builds from October 20) |
| StandBy in the iPhone Duo simulator | missing (known issue) | supported in Device Hub |
| Camera accessory on two screens | known issue | listed as fixed |
| Mac Catalyst build error with iOS 27.1 APIs | known issue | still a known issue |
Then and now
Swift and the macOS requirement stayed where they were. The SDK set is now consistent, where 27.1 mixed one newer iOS SDK with older ones. The rows from StandBy down are where the interesting changes are.
I wrote up the previous release in Xcode 27.1 is out. Three things change when you rebuild, and the release candidate's project format in Xcode 27.2 RC adds a JSON project format. Try it on a branch. The JSON project from that post carries over: Apple's notes say it also opens in earlier Xcode 27 versions.
Device Hub grew up
Apple describes Device Hub as the place in Xcode where every simulated and physical device that shows up as a run destination is managed. It opens as a compact window and expands into a sidebar, a canvas and an inspector, and it has a command-line page too.
The 27.2 notes add a long list to it:
- Touches made through Sidecar, or on a MacBook with touch, reach the remote device as touches, so multi-finger gestures such as pinch and rotate can be tested.
- StandBy works in the iPhone Duo simulator.
- iOS 17 simulator runtimes now accept input.
- Slow Motion Animation, Simulate Shake, Simulate Fall and Simulate Memory Pressure, all simulator-only.
- Smaller things: a context menu for screenshots, hiding the device frame, Secure Keyboard Entry, hardware keyboard simulation and a choice of where captures are saved.
In my Touch on Mac post the way to try touch without the new hardware was an iPad over Sidecar. My take, not Apple's words: the touch support in Device Hub is the first thing I would open if you build for the Mac, because it makes pinch and rotate testable without leaving Xcode.
What closed and what did not
Beyond Device Hub, the notes list fixes in a few places:
- Interface Builder: the toolchain encoded a standard or system
UIStackView.spacingas 0, andUIButtonConfiguration.contentInsetswas not encoded at all. Both are marked fixed. - Previews: the
RenderPreviewMCP tool now lists the available render targets and lets you choose one, and a preview error with CRLF line endings is fixed. - StoreKit Testing: three
SKTestSessionfixes. Intro offer eligibility was not reset afterclearTransactions(), a storefront or locale change did not reachStorefront.updates, and error dialogs could appear whiledialogsDisabledwas true.
The 27.1 known issues are a mixed picture. StandBy and the camera accessory item are closed. Three others, most app extensions not running in the iPhone Duo simulator, a slow first Simulator launch and a missing Mac Catalyst run destination when you target iOS 27.1, are not in the 27.2 notes. The notes do not say they were fixed, so I would not call them resolved.
The Mac Catalyst build error is the one that carries over. Projects that use APIs introduced in iOS 27.1 can fail to build for Mac Catalyst, and both release notes give the same workaround: wrap the code in #if !targetEnvironment(macCatalyst) in Swift, or #if !TARGET_OS_MACCATALYST in Objective-C.
func useNewestAPI() {
#if !targetEnvironment(macCatalyst)
// call the API that only exists in the iOS 27.1 SDK here
print("not running on Mac Catalyst")
#endif
}
Two issues are new in 27.2. The macOS, watchOS, tvOS and visionOS SDKs report 27.1 as a valid deployment target, and building against it can behave unexpectedly. And cloning a simulator that runs a 27.2 runtime can fail because of wrong file permissions. Apple's workaround, from the Xcode and iOS & iPadOS release notes, deletes the leftover files from the source simulator's data folder (replace <SOURCE_UDID> with the simulator you clone from):
find ~/Library/Developer/CoreSimulator/Devices/<SOURCE_UDID>/data -name '*.sb-????????-??????' -delete
Device Hub has known issues too, mostly on iPhone Duo: VoiceOver and the Accessibility Inspector cannot pass screen content, and screenshots and recordings can come out black for a few minutes after launch.
The good and the not-so-good
Good:
- Device Hub covers touch, StandBy on iPhone Duo, iOS 17 input and several simulator tools in one release.
- The camera accessory, Interface Builder and StoreKit Testing fixes are marked fixed in the notes.
Not so good:
- The Mac Catalyst build error with iOS 27.1 APIs is still a known issue.
- Four SDKs report 27.1 as a valid deployment target, and simulator cloning can fail with a 27.2 runtime.
- Several Device Hub gaps remain on iPhone Duo.
My take, not fact: the Device Hub list is the reason to update, and the known issues are the reason to do it on a branch first.
What I would do
My suggestions, not facts:
- Update on a branch and build every target once, Mac Catalyst included. If the 27.1 build error is still there, add the guard above.
- Do not move a deployment target to 27.1 only because the SDK lists it.
- If you clone simulators, keep Apple's delete command at hand.
- If you use storyboards or xibs, check stack view spacing and button content insets after the rebuild.
- In UIKit, the iOS & iPadOS 27.2 notes say a
UIView's default layout margins are zero from iOS 27.1. A child view that should inherit them needspreservesSuperviewLayoutMargins = true. - If your tests use
SKTestSession, rerun them.
Sources
- Xcode 27.2 Release Notes — Apple Developer Documentation — Device Hub improvements and known issues, Interface Builder, Previews and StoreKit Testing fixes, the deployment target and simulator cloning issues, Mac Catalyst
- Xcode 27.1 Release Notes — Apple Developer Documentation — the 27.1 known issues: iPhone Duo simulator, CameraCaptureAccessory, Mac Catalyst
- iOS & iPadOS 27.2 Release Notes — Apple Developer Documentation — simulator cloning workaround, UIKit default layout margins
- Device Hub — Apple Developer Documentation — what Device Hub is and how it is laid out
- Releases — Apple Developer News — release dates and builds of Xcode 27.1 and 27.2, iOS 27.2 on October 26
- Xcode support — Apple Developer — Swift version and SDKs of both releases
- App Store Connect release notes — Apple Developer — builds from Xcode 27.2 accepted for the App Store and TestFlight, and the earlier acceptance of the release candidate
- Xcode 27.1 is out. Three things change when you rebuild — this blog — my earlier post on the previous release
- Xcode 27.2 RC adds a JSON project format. Try it on a branch — this blog — my earlier post on the release candidate
- Touch on Mac: what to check in your app — this blog — my earlier post on testing touch with Sidecar