iOS 27.2 Beta: What Is New for Developers, Beta by Beta

Apple opened the 27.2 cycle on Wednesday, September 16, 2026, two days after iOS 27.0 shipped, with iOS and iPadOS 27.2 beta (24B5084k), matching macOS, tvOS, visionOS, and watchOS betas, and Xcode 27.2 beta (27B5019j); the second betas followed on Monday, September 21 (iOS 27.2 beta 2, 24B5089g), and the third on Monday, October 5 (iOS 27.2 beta 3, 24B5099f). Xcode 27.2 beta 2 (27B5028f) arrived on Monday, September 28, with no new OS beta beside it; the fourth OS betas followed on Tuesday, October 13 (iOS 27.2 beta 4, 24B5110a, with no tvOS beta beside them), and Xcode 27.2 beta 3 (27B5038j) on Wednesday, October 14. The iOS notes are short and, by beta 4, carry two features: the expanded App Tracking Transparency prompt for EU users, whose API beta 3 renames twice, and zero default layout margins for UIView on iOS 27.1 and later. The Xcode notes carry the change most developers will feel first, a JSON project format, plus a deployment-target bug and, in the first beta, a code-completion crash with a workaround; and Apple pointed Duo work to Xcode 27.1 beta in an aside that Xcode 27.2 beta 3 dropped on October 14 without saying the SDK moved; 27.1 has been at its RC since October 5. This post reads the notes beta by beta and will grow with each one.^12357891011

TL;DR

• Builds. iOS and iPadOS 27.2 beta 24B5084k on September 16, beta 2 24B5089g on September 21, and beta 3 24B5099f on October 5; macOS 27.2 beta 2 26B5091g, tvOS 24K5093g, visionOS 24N5093f, watchOS 24S5091f on September 21, and their beta 3 builds 26B5101f, 24K5103f, 24N5103f, 24S5101f on October 5; iOS and iPadOS 27.2 beta 4 24B5110a with macOS 26B5112a, visionOS 24N5114a and watchOS 24S5112a on October 13, and no tvOS 27.2 beta 4 in the feed; Xcode 27.2 beta 27B5019j on September 16, beta 2 27B5028f on September 28 and beta 3 27B5038j on October 14.¹⁷⁸⁹
• Two iOS features by beta 4. “AppTrackingTransparency (ATT) now supports an alternative expanded prompt and re-prompting on a yearly basis for EU users. The alternative prompt is required for users in France, Germany, Italy, Poland, and Romania.” Beta 3 adds the second, in UIKit: “On iOS 27.1 and later, the default layout margins for a UIView are zero.” Beta 3 also renames the expanded-prompt API twice; the name that stands is requestTrackingAuthorizationPreferringExpandedInterface. The rest of the iOS notes is three StoreKit Testing fixes, one StoreKit Testing known issue, one Health known issue, one Shortcuts known issue, and, new in beta 3, a simulator-cloning known issue and a Quest lab appointments known issue. No deprecations, and no change the notes tie to linking against the 27.2 SDK.²⁸ Beta 4’s page is beta 3’s with the build name changed in the Overview: the same entries under the same radar numbers.¹⁰
• The Xcode change that matters. “Xcode now supports a JSON-based project format (.xcproj) that’s more readable, merge-friendly, and easier for coding agents to edit. Enable it in the file inspector. Projects using .xcproj also open in earlier versions of Xcode 27.”³
• Two Xcode traps. The macOS, watchOS, tvOS, and visionOS SDKs in 27.2 “incorrectly report 27.1 as a valid deployment target,” and Xcode “may crash when using code completion on macOS 27.2 beta,” with a defaults write workaround. The beta 2 and beta 3 notes keep the first and no longer list the second.³⁷¹¹
• Not in 27.2. The iPhone Duo SDK and simulator: “Download Xcode 27.1 beta to get the iOS SDK and simulator support for iPhone Duo,” an aside removed in Xcode 27.2 beta 3 on October 14 with nothing in its place, and Apple’s news post says the phone ships October 23 on iOS 27.1.³⁵¹¹

Which build is which?

The order is the story. Apple went to 27.2 betas before any 27.1 beta existed, and then shipped Xcode 27.1 beta two days later as the release that carries iPhone Duo; the Xcode 27 post has the timeline and the Duo simulator post has the hands-on. As of September 26 there is still no iOS 27.1 page in Apple’s release-notes index, only “iOS & iPadOS 27 Release Notes” and “iOS & iPadOS 27.2 Beta 2 Release Notes.”¹² As of October 14 the feed has no tvOS 27.2 beta 4, the only system without a fourth beta.⁹

What do the iOS 27.2 beta notes say?

The beta 2 page opened with the scope sentence, “The iOS & iPadOS 27.2 SDK provides support to develop apps for iPhone and iPad running iOS & iPadOS 27.2 beta 2. The SDK comes bundled with Xcode 27.2,” and then ran four areas.²

App Tracking Transparency. The page’s one New Feature was: “AppTrackingTransparency (ATT) now supports an alternative expanded prompt and re-prompting on a yearly basis for EU users. The alternative prompt is required for users in France, Germany, Italy, Poland, and Romania.” The note names no API. My EU tracking prompt post reads the header and the reference page for what the note leaves out, the new requestTrackingAuthorization overload that buys the expanded sheet in the rest of the EU and the “Additional Information” button that dismisses without recording a decision, and runs a probe on the beta simulator, where every run that prompted, on the first beta’s runtime, showed the standard alert and never the sheet; the sheet itself is a device test, on a device located in the EU and signed in with an EU-region Apple Account.

StoreKit Testing in Xcode. Two entries move from the 27.0 notes’ Known Issues to Resolved: “Changing the storefront or locale using SKTestSession doesn’t propagate through Storefront.updates,” and “Failed purchases using SKTestSession might display error dialogs even when dialogsDisabled is set to true.” A third Resolved entry, “Intro offer eligibility does not reset immediately after calling SKTestSession.clearTransactions(),” repeats a fix the 27.0 notes already list. One new Known Issue: “Making a purchase in-app for a subscription that is a member of a subscription bundle incorrectly allows the user to unbundle instead of throwing an error.”²

Health and Shortcuts. Two Known Issues: “Personalized summaries may not generate as expected in the Insights tab,” and “Describe a Shortcut might fail with the error “Something went wrong. Try again later.””²

That was the whole beta 2 page. Between beta 1 and beta 2 the sections and radar numbers did not change, per the iOS 27 notes post’s September 21 update; the title and the Overview’s build name did, from “Beta” to “Beta 2.” On the Xcode 27.2 page, the Overview sentence that promised the Duo SDK “later this month in an upcoming release of Xcode 27.1” was replaced by the download aside between September 17 and 19, as the same post records in its September 19 update and footnote 8; the aside is quoted from the page as fetched September 26.³ Every 27.0 deprecation and linked-on-27 behavior change in that post stands unchanged in 27.2 beta 2.²

What does Xcode 27.2 beta change?

The Overview: “Xcode 27.2 beta includes Swift 6.4 and SDKs for iOS 27.2, iPadOS 27.2, tvOS 27.2, watchOS 27.2, macOS 27.2, and visionOS 27.2. Xcode 27.2 beta supports on-device debugging in iOS 17 and later, tvOS 17 and later, watchOS 10 and later, and visionOS. Xcode 27.2 beta requires a Mac running macOS Tahoe 26.6 or later.” Under it sat the aside, until beta 3 removed it (below): “Download Xcode 27.1 beta to get the iOS SDK and simulator support for iPhone Duo.”³

The JSON project format. Under Project Format, New Features: “Xcode now supports a JSON-based project format (.xcproj) that’s more readable, merge-friendly, and easier for coding agents to edit. Enable it in the file inspector. Projects using .xcproj also open in earlier versions of Xcode 27. Learn more in Updating your Xcode project configuration file format.” Three things in three sentences: the format is opt-in per project, it is backward compatible within the 27 line, and Apple names coding agents as a reason. Anyone whose agent has spent turns editing project.pbxproj by regex knows why the coding-agents clause is there; the merge-friendliness is the part teams have wanted for a decade. I have not converted a project yet, so what the file looks like on disk is for a later note.³

The deployment-target trap. Under SDK, Known Issues: “macOS, watchOS, tvOS, and visionOS SDKs in Xcode 27.2 incorrectly report 27.1 as a valid deployment target. Builds and other functionality may have unexpected behavior if this deployment target is used. Mac Catalyst builds with a 27.1 or 27.2 deployment target may be unable to use newly introduced API.” Apple has released no 27.1 for those four systems, and the Xcode 27.1 beta’s own Overview lists their SDKs at 27, so a target set to 27.1 requires an OS version Apple has not shipped. Use 27.0, or 27.2 only for a target meant to require the beta, and keep Apple’s Mac Catalyst caveat in view for both 27.1 and 27.2.³⁶

The code-completion crash. Under General, Known Issues: “Xcode may crash when using code completion on macOS 27.2 beta,” with the workaround defaults write com.apple.dt.Xcode CodeCompletionAssetsToLoad /dev/null, which “turn[s] off enhanced code completion ranking.” The macOS 27.2 beta 2 notes list the crash as fixed on the OS side, so a Mac on beta 2 should not need the default.³⁴

Device Hub and Simulator. Two Device Hub Known Issues: keyboard and mouse input to simulators “for OS versions before iOS 18.0, tvOS 18.0, watchOS 11.0, and visionOS 2.0” is not accepted, and a physical device disconnected while “Simulate Hardware Keyboard” was on “may remain in “hardware keyboard” mode for up to 2 minutes.” One Simulator Known Issue with an old radar: “Some simulator runtimes are not completely deleted when removed, re-appearing after a reboot.”³ All three are listed as fixed in beta 2, below.⁷

Previews. Four fixes, one of them for agents: “The RenderPreview MCP tool now returns the list of available render destinations, and lets the caller specify which destination to use for rendering.” The others are a thumbnail-grid selection bug, a clearer error for unsupported platforms, and a clearer error “when previews fail because another user account on this Mac owns the Previews JIT directory.”³

What does Xcode 27.2 beta 2 change?

Xcode 27.2 beta 2 (27B5028f) is dated Monday, September 28 in the releases feed, with no 27.2 OS beta beside it; the other operating-system items that day are the 27.0.1 updates for iOS, iPadOS, macOS, visionOS, and watchOS, and iPadOS 26.7.1.⁷ I read the retitled page on October 1 against my September 26 copy of the first beta’s. The Overview reads the same with “beta 2” in place of “beta” in each sentence, the same SDKs and the same macOS 26.6 requirement, and the Duo aside is unchanged. Apple also folded the first beta’s Previews & Playgrounds section into Previews and moved two first-beta Previews fixes under a new “Updates in Xcode 27.2 Beta” heading; the RenderPreview and JIT-directory fixes stay in the top section, though both shipped in the first beta. I have not installed beta 2, so everything in this section is Apple’s text.⁷

One new tool for agents. Under Coding Assistant, New Features: “Added a GetCodeCoverage MCP tool that reports code coverage from the most recent test result, optionally filtered by target or file.” With the RenderPreview fix above, that is two beta notes in a row extending what an agent connected to Xcode can ask for.⁷

Device Hub gets its input back. The two Device Hub Known Issues from the first beta now sit under Resolved Issues with “Fixed:” in front: simulator keyboard and mouse input “for OS versions before iOS 18.0, tvOS 18.0, watchOS 11.0, and visionOS 2.0,” and the two-minute “hardware keyboard” hangover. Two more fixes sit beside them: “Fixed an issue where Device Hub stopped sending touch and button input to a connected device after a period of inactivity,” and “Fixed: Device Hub now supports input to iOS 17 Simulator Devices.” The old Simulator entry about runtimes “re-appearing after a reboot” is listed as fixed too.⁷

Two fixes outside Device Hub. A new Devices section lists “Fixed: Holding Escape does not dismiss keyboard capture mode,” and Previews adds “Fixed an issue where previews could fail in source files that use Windows-style (CRLF) line endings.” If your repository carries CRLF files, that second one is the reason to try beta 2.⁷

The code-completion crash is gone from the page. The General Known Issue about code completion on macOS 27.2 beta, with its defaults write workaround, appears nowhere in the beta 2 notes, under Known Issues or Resolved Issues. The macOS 27.2 beta 2 notes had already listed the crash as fixed on the OS side.⁴ If you set the default, defaults delete com.apple.dt.Xcode CodeCompletionAssetsToLoad removes it; that command is mine, not Apple’s.

iPhone Duo appears in a release Apple says does not carry it. The aside still reads “Download Xcode 27.1 beta to get the iOS SDK and simulator support for iPhone Duo.” Yet two new Known Issues name the phone: “Screenshots and recordings in iPhone Duo may be black for up to a few minutes after booting the device,” and “VoiceOver, the Accessibility Inspector, and other accessibility tools cannot convey screen content on an iPhone Duo within Device Hub.” Two more entries are word for word from the Xcode 27.1 beta notes: the Mac Catalyst Known Issue, “Projects that use APIs specific to iOS 27.1 show compile errors when building for Mac Catalyst,” with its #if !targetEnvironment(macCatalyst) workaround, and the Previews feature, “The canvas overrides picker now includes a Display group for previewing content on a device’s alternative display.”⁶⁷ The page does not explain the overlap, and its Overview still lists an iOS 27.2 SDK and no 27.1. Until Apple says otherwise I would keep doing what the aside says and build for Duo in 27.1 beta.

Still open, and new. The deployment-target Known Issue is unchanged under the same radar number. New Known Issues: “Cloning a 27.2 simulator device may encounter an issue due to incorrect file permissions”; Device Hub may “quit unexpectedly” when you select a Vision Pro simulator with no visionOS runtime installed; “The Device->Simulate Memory Warning menu item does not work”; CarPlay in Device Hub “requires devices to be physically connected via USB cable (not over the network)”; and a simulator runtime re-installed after deletion “may still show up as unavailable in Xcode,” with killall -9 com.apple.CoreSimulator.CoreSimulatorService as Apple’s workaround. One entry appears misfiled: “Fixed an issue where modifier keys such as Shift, Control, Option, and Command were not sent to the correct device when more than one device window was open” sits under Device Hub’s Known Issues heading.⁷

What do the iOS 27.2 beta 3 notes say?

iOS and iPadOS 27.2 beta 3 (24B5099f) is dated Monday, October 5 in the releases feed, with macOS 27.2 beta 3 (26B5101f), tvOS 27.2 beta 3 (24K5103f), visionOS 27.2 beta 3 (24N5103f), and watchOS 27.2 beta 3 (24S5101f) the same morning. The Xcode item that day is Xcode 27.1 RC (27A9275); the feed listed no Xcode 27.2 after beta 2 (27B5028f) of September 28 as of October 11. Xcode 27.2 beta 3 followed on October 14.⁸⁹ Apple replaced the beta 2 page at the same URL, and I read it on October 11 against the beta 2 text quoted above. The Overview now names “iOS & iPadOS 27.2 beta 3” and still says “The SDK comes bundled with Xcode 27.2.” Five entries are new: two App Tracking Transparency fixes, one UIKit feature, and two Known Issues. Every entry from the beta 2 page is still there. I have not installed beta 3, so this section is Apple’s text, apart from one SDK header I name below.⁸

The tracking API has had three names. Under App Tracking Transparency, two new Resolved Issues: “Fixed: The new requestTrackingAuthorization(usingExpandedInterface:additionalInformationAction:completionHandler:) API is renamed to requestTrackingAuthorization(preferExpandedInterface:...). (187149729)” and “Fixed: The new requestTrackingAuthorization(preferExpandedInterface:...) API is renamed to requestTrackingAuthorizationPreferringExpandedInterface:…). (187610745)” In order, the names are:

1. requestTrackingAuthorization(usingExpandedInterface:additionalInformationAction:completionHandler:), the name the first beta’s SDK declares. I read it in the ATTrackingManager.h header of the iOS 27.2 SDK in Xcode 27.2 beta (27B5019j), as the Objective-C method requestTrackingAuthorizationUsingExpandedInterface:additionalInformationAction:completionHandler:.
2. requestTrackingAuthorization(preferExpandedInterface:...).
3. requestTrackingAuthorizationPreferringExpandedInterface, the name the beta 3 notes leave standing.

Apple prints the third name half Objective-C and half Swift, with a colon and a stray closing parenthesis, and shortens the second with an ellipsis, so the notes give neither one’s full signature. They also do not say whether the earlier names survive as deprecated spellings. I have read only the first beta’s header (27B5019j), not Xcode 27.2 beta 2’s (27B5028f), so I have not seen a header that declares the third name. Until I do, treat any call to the first name, including the one in my EU tracking prompt post, as code that will change, and read the new header before you ship. The feature entry itself (179504171) is word for word the beta 2 entry.⁸

A UIKit change for iOS 27.1 and later. The page’s second New Feature, where beta 1 and beta 2 had one: “On iOS 27.1 and later, the default layout margins for a UIView are zero. A view controller continues to provide its view with systemMinimumLayoutMargins, which vary depending on the presentation context. To inherit these margins in a subview of the view controller’s view, set its preservesSuperviewLayoutMargins property to true. (186294594)” The entry names iOS 27.1, the release iPhone Duo ships on, rather than 27.2, and it does not say whether the change depends on the SDK an app links against.⁵⁸ A subview that lays out against its own layout margins and relied on the default ones gets zero margins on iOS 27.1 and later; Apple’s remedy is preservesSuperviewLayoutMargins.

Cloning a 27.2 simulator device. Under a new Simulator Runtimes heading, a Known Issue: “Cloning a simulator device running runtime 27.2 might fail due to incorrect file permissions. (188407822) (FB24939277)” It carries the same radar number as the Xcode 27.2 beta 2 Known Issue quoted above, and the OS page adds Apple’s workaround: find ~/Library/Developer/CoreSimulator/Devices/<SOURCE_UDID>/data -name '*.sb-????????-??????' -delete. The command deletes files, so replace <SOURCE_UDID> with the identifier of the device you clone from before you run it; xcrun simctl list devices prints the identifiers, and that pointer is mine, not Apple’s.⁷⁸

Quest lab appointments. A Known Issue under its own heading, addressed to the person holding the phone: “If you have an upcoming lab appointment, wait to update iOS versions until you receive your results. Contact Quest directly to reschedule your appointment if you run into any issues. (184530996)” The workaround: “Lab results are also available under Browse > Lab Results.” If your test device is also the phone you use, it applies to you.⁸

Carried over, and nothing dropped. The Health and Shortcuts Known Issues, the three StoreKit Testing fixes, and the subscription-bundle Known Issue are on the beta 3 page under the same radar numbers as in beta 2 (186964423, 187499433, 183933307, 184155259, 184255116, 186018916); the intro-offer fix also carries Feedback number FB24137836. No entry from the beta 2 page is missing from the beta 3 page.²⁸

What do the iOS 27.2 beta 4 notes say?

iOS and iPadOS 27.2 beta 4 (24B5110a) is dated Tuesday, October 13 in the releases feed, at 10:00 Pacific, with macOS 27.2 beta 4 (26B5112a), visionOS 27.2 beta 4 (24N5114a) and watchOS 27.2 beta 4 (24S5112a) the same hour, and no tvOS 27.2 beta 4 then or since; the week’s Xcode item came the next day. Apple replaced the beta 3 page at the same URL, and I read it on October 13 and again on October 14 against the beta 3 text above. The Overview now reads “iOS & iPadOS 27.2 beta 4”, and the rest of the page is the beta 3 page: the same App Tracking Transparency feature and two renames, the same Health, Quest Lab Appointments, Shortcuts and Simulator Runtimes Known Issues, the same three StoreKit Testing fixes and one Known Issue, and the same UIKit margins feature, each under the radar number footnote 8 lists. Nothing added, nothing dropped, so the third name of the tracking API still stands and the header question above is still open. I have not installed beta 4.⁹¹⁰

What does Xcode 27.2 beta 3 change?

Xcode 27.2 beta 3 (27B5038j) is dated Wednesday, October 14 in the releases feed, at 10:00 Pacific, the day after the fourth OS betas and sixteen days after beta 2. I read the retitled page on October 14 against the beta 2 text quoted above. The Overview reads the same with “beta 3” in place of “beta 2”, the same six SDKs, a tvOS 27.2 SDK among them though the feed has no tvOS 27.2 beta 4, and the same macOS 26.6 requirement. App Store Connect’s release notes carry a TestFlight entry dated the same day: “You can now submit apps built with Xcode 27.2 beta 3 using the SDK for iOS 27.2 beta 4, iPadOS 27.2 beta 4, macOS 27.2 beta 4, tvOS 27.2 beta 3, visionOS 27.2 beta 4, and watchOS 27.2 beta 4 for internal and external testing.” The entry names the tvOS SDK as beta 3’s and says nothing about the store. I have not installed beta 3, so this section is Apple’s text.⁹¹¹¹³

The Duo aside is gone. The aside that has sat under the Overview since September 19 at the latest is not on the beta 3 page: “Download Xcode 27.1 beta to get the iOS SDK and simulator support for iPhone Duo.” Nothing replaces it: the Overview still lists an iOS 27.2 SDK and no 27.1, the two iPhone Duo Known Issues from beta 2 are still there under General and Device Hub, and the Mac Catalyst entry about “APIs specific to iOS 27.1” is unchanged. Whether the 27.2 beta 3 SDK carries the Duo APIs, the page does not say, and I have not opened the SDK. Until Apple says otherwise, Xcode 27.1 is the Duo build: the aside said so, naming its beta, until October 14, and the 27.1 RC notes of October 5 carry the iOS 27.1 SDK and the Duo simulator entries.¹¹⁸

Interface Builder, two fixes. A new section, Resolved Issues: “Fixed: Interface Builder toolchain compilation mode incorrectly encoded standard/system UIStackView.spacing as 0.” and “Fixed: Interface Builder toolchain compilation mode failed to encode UIButtonConfiguration.contentInsets.” Both carry Feedback numbers (FB24605403 and FB24829108), so both were reported through Feedback Assistant. If a storyboard’s stack views lost their spacing, or a button its content insets, under the toolchain compilation mode, beta 3 is the build to retest on.¹¹

The cloning issue moves and gains a command. Beta 2’s General Known Issue, “Cloning a 27.2 simulator device may encounter an issue due to incorrect file permissions”, now sits under a new Simulator Runtimes heading as “Cloning a simulator device running runtime 27.2 might fail due to incorrect file permissions.” That is the wording of the iOS 27.2 beta 3 notes, and the same find command is its workaround, so the caution above about replacing <SOURCE_UDID> before running it applies.¹¹

Two entries change state. The runtime that “may still show up as unavailable in Xcode” after being deleted and re-installed, a Simulator Known Issue on the beta 2 page with killall -9 com.apple.CoreSimulator.CoreSimulatorService as its workaround, is now prefixed “Fixed:” and filed under “Resolved Issues in Xcode 27.2 Beta 2”, and the killall line is gone. The modifier-keys fix that the beta 2 page listed under Device Hub’s Known Issues, which I called misfiled above, is under “Resolved Issues in Xcode 27.2 Beta 2” as well. Apple also moved every beta 2 feature and fix, with the two newly resolved entries, under an “Updates in Xcode 27.2 Beta 2” heading, with “in Xcode 27.2 Beta 2” appended to each subheading, the pattern the page already used for the first beta’s entries; the open Known Issues stay at the top. The move carries three first-beta entries with it, the .xcproj format and the RenderPreview and JIT-directory fixes, the last two of which I noted above as staying in the top section, so Apple’s page now files the post’s headline Xcode 27.2 feature under beta 2.¹¹

Still open. The deployment-target Known Issue is unchanged under 187160501; the Simulator entry that CarPlay in Device Hub “requires devices to be physically connected via USB cable (not over the network)” is still there; the Vision Pro simulator crash, the memory-warning menu item and the two iPhone Duo entries are still Known Issues under the same numbers; and the code-completion crash is still absent from the page.¹¹

What do the macOS 27.2 beta 2 notes say?

Five sections. The code-completion crash listed as fixed; one AppKit deprecation, “The EnablePasteboardPrivacyDeveloperPreview user default has been removed”; a Notifications Known Issue on clean installs, where Macs “might not prompt you to allow notifications for some apps, such as Calendar, Maps, Find My, Home, and Weather,” with System Settings as the workaround; the same Shortcuts Known Issue as iOS; and the same StoreKit Testing entries as iOS, three fixed and one new. The macOS 27 notes post covers the 27.0 release the beta builds on.⁴ Update, October 14: the page is now titled for beta 4 and is otherwise the beta 3 page. One entry is new since beta 2, and it was already on the beta 3 page on October 11, a Display Settings Known Issue: “When an external display is connected, display settings might not be restored correctly, and the display arrangement might change.” Beta 4 adds nothing, and every beta 2 entry stands under its radar number.¹²

What is not in 27.2?

iPhone Duo. Apple’s September 16 news post says: “When iPhone Duo becomes available on October 23, it will run iOS 27.1. This version builds on the foundation of iOS 27 and introduces features that were purpose-built for the new foldable design. Xcode 27.1 will add development support for iPhone Duo. This includes updated SDKs and a simulator that supports the all-new poses and orientations of iPhone Duo.” The Xcode 27.2 beta notes repeat the pointer. So a 27.2 beta install tests the EU prompt and the StoreKit fixes; it does not test a fold, and a project that needs both the Duo APIs and the 27.2 SDK is waiting on a build Apple has not published, going by the aside; the beta 2 notes’ unexplained Duo entries, above, are the one sign that this may change.³⁵⁷ Update, October 14: Xcode 27.2 beta 3 removes the aside and says nothing in its place; the Overview still lists an iOS 27.2 SDK, the Duo known issues stay, and whether beta 3’s SDK carries the Duo APIs is not stated. Xcode 27.1 remains the Duo build: the aside said so until October 14, and the 27.1 RC notes carry the iOS 27.1 SDK and the Duo simulator entries.¹¹⁸

What I would do this week

1. If you sell in the EU, and you must if you sell in France, Germany, Italy, Poland, or Romania, check your tracking flow on a device located in the EU and signed in with an EU-region Apple Account; the simulator showed only the standard alert in my runs, and the EU tracking prompt post has the ship steps and the one return value that is neither a yes nor a no.²
2. Try .xcproj on a branch, not on main: enable it in the file inspector, commit, and see what a merge conflict looks like in the new file before the team adopts it.³
3. Check every target’s deployment menu in Xcode 27.2 for a 27.1 that should not be there on macOS, watchOS, tvOS, and visionOS.³
4. If StoreKit tests around storefront changes or dialogsDisabled were flaky under 27.0, rerun them on 27.2; both causes are listed as fixed.²
5. Keep Xcode 27.1 (the RC, 27A9275, since October 5; before that, 27.1 beta) installed beside 27.2 beta if you build for Duo; neither one replaces the other yet. Xcode 27.2 beta 3 dropped the aside that pointed at 27.1 on October 14 without saying the SDK moved.³⁵⁸¹¹
6. If you drive simulators older than iOS 18 through Device Hub, or your previews fail on files with CRLF line endings, Xcode 27.2 beta 2 lists those fixes. If you set the code-completion default for the first beta, Apple lists the crash as fixed in macOS 27.2 beta 2; on that build, my defaults delete com.apple.dt.Xcode CodeCompletionAssetsToLoad removes the setting Apple’s workaround added.⁴⁷
7. If a storyboard lost its stack-view spacing or a button its content insets under Interface Builder’s toolchain compilation mode, retest on Xcode 27.2 beta 3, which lists both as fixed.¹¹

FAQ

What is new in iOS 27.2 beta 2?

The same page as beta 1 with a new title and build name in the Overview: the expanded EU App Tracking Transparency prompt, three StoreKit Testing fixes, and three known issues. No deprecations and no behavior changes gated on the 27.2 SDK.²

What is new in iOS 27.2 beta 3?

Build 24B5099f, dated October 5: a UIKit feature, “On iOS 27.1 and later, the default layout margins for a UIView are zero”; two App Tracking Transparency fixes that rename the expanded-prompt API; and two known issues, one for cloning a simulator device on the 27.2 runtime and one for Quest lab appointments. Every beta 2 entry carries over under the same radar number.⁸

What is new in iOS 27.2 beta 4?

Build 24B5110a, dated October 13: nothing on the page but the build name. Every beta 3 feature, fix and known issue is there under the same radar number, and no entry is added or dropped; there is no tvOS 27.2 beta 4 in the feed.⁹¹⁰

What is the expanded tracking prompt API called?

It has had three names. The first beta’s SDK declares requestTrackingAuthorization(usingExpandedInterface:additionalInformationAction:completionHandler:). Apple’s beta 3 notes rename it to requestTrackingAuthorization(preferExpandedInterface:...) and then to requestTrackingAuthorizationPreferringExpandedInterface, the name that stands. Apple abbreviates the last two. Xcode 27.2 beta 3 (27B5038j) arrived on October 14; I have not opened its header, so I have not read one that declares the new names. Read the new header before you ship.⁸⁹

When will iOS 27.2 be released?

Apple has not announced a date. The betas began September 16, reached beta 2 on September 21, beta 3 on October 5 and beta 4 on October 13, with Xcode 27.2 beta 2 on September 28 and beta 3 on October 14; this post will carry the release when the feed does.¹⁷⁸⁹

What is new in Xcode 27.2 beta 2?

Build 27B5028f, dated September 28: a GetCodeCoverage MCP tool, four Device Hub input fixes, a Previews fix for source files with CRLF line endings, a fix for Escape not dismissing keyboard capture, a fix for simulator runtimes that came back after deletion, and several new known issues around Device Hub and Simulator. The code-completion crash from the first beta is no longer listed, and the deployment-target known issue remains.⁷

What is new in Xcode 27.2 beta 3?

Build 27B5038j, dated October 14: two Interface Builder fixes for the toolchain compilation mode, the simulator-cloning issue moved under a Simulator Runtimes heading with the find command as its workaround, the runtime-reinstall issue and the misfiled modifier-keys entry refiled as resolved in beta 2, and the Duo aside removed without a replacement. The deployment-target, CarPlay, Vision Pro simulator and iPhone Duo known issues remain.¹¹

Is iPhone Duo supported in the iOS 27.2 beta?

Not by Apple’s word. The Duo SDK and simulator ship in Xcode 27.1 beta (October 11: in the 27.1 RC, 27A9275, since October 5), and the phone runs iOS 27.1 at launch on October 23, per Apple.³⁵⁸ The Xcode 27.2 beta 2 notes do list two iPhone Duo known issues and the alternative-display preview group, without explaining them; Apple’s aside sent Duo work to 27.1 beta until Xcode 27.2 beta 3 removed it on October 14, without saying where the SDK lives.⁷¹¹

What is the .xcproj format?

A JSON-based Xcode project format introduced in Xcode 27.2 beta, opt-in per project through the file inspector, that Apple describes as “more readable, merge-friendly, and easier for coding agents to edit,” and that earlier versions of Xcode 27 can still open.³

Should I install the 27.2 beta on a device I use?

The notes list the known issues above and nothing about data loss, but the beta is a beta. The EU sheet needs a device located in the EU and signed in with an EU-region Apple Account; the simulator showed only the standard alert in my runs. The StoreKit Testing fixes are listed in the 27.2 OS notes, so a 27.2 simulator runtime should be enough to rerun those tests without a device install.²

Sources