iOS 27.2 Release Notes: What Shipped, and Where 27.1 Went

iOS 27.2 and iPadOS 27.2 shipped on Monday, October 26, 2026 as build 24B119, at 10:00 Pacific in Apple’s releases feed, beside a second iOS 27.2 build, 24B91020, that Apple lists without saying which phone it is for. macOS 27.2 Golden Gate (26B123), tvOS 27.2 (24K122), visionOS 27.2 (24N120), watchOS 27.2 (24S118), and security updates back to iOS 18.7.11 landed in the same minute; Xcode 27.2 did not, and is still the October 19 release candidate (27B48).¹⁸ The developer notes are the beta 4 page plus two Known Issues: 8 headed areas, 2 new features, 5 resolved issues, 7 known issues, and no deprecations, and nothing the notes tie to the SDK an app links against; one entry is tied to it anyway, since a probe linked against the 27.1 SDK gets zero default UIView margins on the iOS 27.1 runtime and the same source linked against 27.0 keeps 8 points.²⁴ The release also closes a question six weeks old. iOS 27.1 shipped on October 23, on iPhone Duo and on nothing else: Apple’s security page lists it for “iPhone Duo” alone, its release-notes page never appeared, and the 27.1 simulator runtime on this Mac accepts exactly one device type.⁴⁵⁶

TL;DR

• Builds. Device 24B119 for iOS and iPadOS 27.2, with a second iOS 27.2 build, 24B91020, listed first in the feed. The SDK is still the RC’s: Xcode 27.2 RC (27B48) of October 19, which App Store Connect has accepted for the App Store since October 20. The only 27.2 runtime on this Mac is the first beta’s, 24B5084k, so the SDK and simulator numbers in the table below are not the release’s.¹³⁴
• Two features, five fixes, seven known issues. The expanded App Tracking Transparency prompt for EU users, required in France, Germany, Italy, Poland, and Romania, and zero default layout margins for UIView “on iOS 27.1 and later.” Three StoreKit Testing fixes and two renames of the tracking API are the resolved issues. New since beta 4: a Nearby Interaction timeout and a Health entry that still says “this beta.”²
• The tracking API has its name. Apple’s reference page now titles the method requestTrackingAuthorization(preferExpandedInterface:additionalInformationAction:completionHandler:), for iOS 27.2, iPadOS 27.2, and Mac Catalyst 27.2 with no beta badge, and the page for the first beta’s name returns 404. No header on this Mac declares it; the Xcode 27.2 RC, whose SDK should, is not installed here.¹⁰
• The margins entry is real, and it is gated on the SDK. One UIKit source built with three SDK stamps: stamped for the 27.0 SDK it reports 8-point default margins on every runtime here; stamped for the 27.1 or the 27.2 SDK it reports zero on the iOS 27.1 runtime (24A94425, on an iPhone Duo simulator) and 8 on the first iOS 27.2 beta runtime and on iOS 18.5. The entry names the OS and not the SDK; the probe says both conditions apply. A simulator is not the phone, and the 27.2 release runtime is not installed here.⁴
• iOS 27.1 was the phone’s alone. Apple’s security releases page: “iOS 27.1”, “iPhone Duo”, “23 Oct 2026”, “This update has no published CVE entries.” No feed item, no notes page, no section on Apple’s “About iOS 27 Updates” page, and a simulator runtime whose supported device list has one entry. Apple’s pages do not say “only”; the reading is mine from those listings, and press reports said the same on launch day.⁴⁵⁷¹¹
• 162 CVEs. The iOS 27.2 security content page lists 162 CVE-2026 entries and one from 2022 across 67 components, WebKit first with 26; the page uses neither “exploited” nor “actively.” iOS 26.7.2 carries 133 for the older line.⁵

Which build is which?

The feed tells two things by what it leaves out. The Xcode 27.2 RC item is lettered g for October 19, so six items preceded it that morning, and none survives in today’s feed. A copy of the feed saved this morning at 11:28 Pacific still has them: “iOS 27.2 RC (24B115)”, “iPadOS 27.2 RC (24B115)”, “macOS 27.2 RC (26B118)”, “tvOS 27.2 RC (24K120)”, “visionOS 27.2 RC (24N118)”, and “watchOS 27.2 RC (24S116)”, lettered a through f. The release items replaced them the way the Xcode 27.1 release replaced its RC item on October 15, and the device build moved from 24B115 to 24B119 between the RC and the release. And across 43 items back to May 11, no operating-system title contains “27.1”. The 27.0 notes post found the same absence in September and the 27.2 beta post tracked it through four betas; today it is settled, in the section on iPhone Duo below.¹

The notes themselves open with the scope sentences the beta pages used, now without a beta name: “The iOS & iPadOS 27.2 SDK provides support to develop apps for iPhone and iPad running iOS & iPadOS 27.2. The SDK comes bundled with Xcode 27.2.” Apple’s page was last modified at 07:18 Pacific, before the feed items. The release-notes index lists two entries for the 27 line, “iOS & iPadOS 27 Release Notes” and “iOS & iPadOS 27.2 Release Notes.”²

What do the 27.2 notes say?

Counting list items under each heading, the way the 27.0 post counted its 93 areas, gives 8 areas with 2 new features, 5 resolved issues, 7 known issues, and no Deprecations heading. Workarounds are not counted. Compared with the beta 4 page I read on October 14, every entry carries over under the same radar number, one heading is renamed, and two Known Issues are new.²

App Tracking Transparency. The feature: “AppTrackingTransparency (ATT) now supports an alternative expanded prompt and reprompting on a yearly basis for EU users. The alternative prompt is required for users in France, Germany, Italy, Poland, and Romania. (179504171)” The two Resolved Issues are the renames: “Fixed: The new requestTrackingAuthorization(usingExpandedInterface:additionalInformationAction:completionHandler:) API is renamed to requestTrackingAuthorization(preferExpandedInterface:...). (187149729)” and “Fixed: The new requestTrackingAuthorizationPreferExpandedInterface:... API is renamed to requestTrackingAuthorizationPreferringExpandedInterface:.... (187610745)” The second entry is written as an Objective-C selector on both sides, where the beta 3 page had mixed the two languages, and it reads cleanly now: the Swift method is requestTrackingAuthorization(preferExpandedInterface:additionalInformationAction:completionHandler:), and its Objective-C selector begins requestTrackingAuthorizationPreferringExpandedInterface:. Apple’s reference page agrees with the Swift half, and the next section reads it.²¹⁰ My EU tracking prompt post has the Info.plist key, the “Additional Information” button that dismisses without recording a decision, and the ship steps.

UIKit. The one other feature, unchanged from beta 3: “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 the operating system and says nothing about the SDK an app links against, and the version it names, 27.1, exists only on iPhone Duo. I ran it; the section after next has the result, and the SDK turns out to matter.²

StoreKit Testing in Xcode. Three fixes and one Known Issue, all carried from the betas: “Fixed: Intro offer eligibility does not reset immediately after calling SKTestSession.clearTransactions(). (183933307) (FB24137836)”, “Fixed: Changing the storefront or locale using SKTestSession doesn’t propagate through Storefront.updates. (184155259)”, and “Fixed: Failed purchases using SKTestSession might display error dialogs even when dialogsDisabled is set to true. (184255116)”; still open, “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. (186018916)”. The two middle fixes were Known Issues in the 27.0 notes, so a StoreKit test that was flaky around storefront changes under 27.0 has its fix on a shipped notes page now, and in the simulator runtime once Xcode 27.2 ships it; a device on 27.2 has it today.²

Nearby Interaction, new. “An NISession running with a DL-TDoA configuration in a foreground app might be invalidated unexpectedly with a resource timeout error (NIErrorCodeResourceUsageTimeout). (189664070)” Workaround: “Run a new NISession with the same DL-TDoA configuration.” DL-TDoA is the downlink time-difference-of-arrival mode for ultra-wideband positioning against installed anchors; if your app uses it, the session you hold can die with that error code and the remedy is to start another.²

Health, one new. The entry that was there since the first beta, now “Personalized summaries might not generate as expected in the Insights tab. (186964423)”, and a new one that Apple did not rewrite for the release: “The redesigned Health app is not included in this beta and was available in the previous beta for testing purposes only. If you update to this beta, your Health app data from the previous beta remains on your device and is viewable in Settings. The redesigned Health app will be available again in an upcoming iOS beta. (188843443)” Read literally on a release page, it says the redesigned Health app is not in iOS 27.2 and will return in a later beta. Apple’s customer-facing notes for 27.2 do not mention Health at all.²⁷

Shortcuts, Quest Lab Appointments, Simulator. “Describe a Shortcut might fail with the error “Something went wrong. Try again later.” (187499433)”; “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)”, with lab results also “under Browse > Lab Results”; and, under a heading now called Simulator where beta 3 called it Simulator Runtimes, “Cloning a simulator device running runtime 27.2 might fail due to incorrect file permissions. (188407822) (FB24939277)”, with Apple’s workaround, find ~/Library/Developer/CoreSimulator/Devices/<SOURCE_UDID>/data -name '*.sb-????????-??????' -delete. The command deletes files; put the source device’s identifier in place of <SOURCE_UDID> before you run it, and xcrun simctl list devices prints the identifiers.²

What changes the moment you build with the 27.2 SDK?

By the notes, nothing. The 27.0 notes had 23 entries that fire on the first archive from the new SDK; the 27.2 notes have none phrased “in apps built with the 27.2 SDK.” By the probe in the next section, one. The tracking API is gated by availability: the first beta’s header marks requestTrackingAuthorizationUsingExpandedInterface:additionalInformationAction:completionHandler: API_AVAILABLE(ios(27.2)) API_UNAVAILABLE(macos, tvos, watchos, visionos), and the reference page for the renamed method lists iOS 27.2, iPadOS 27.2, and Mac Catalyst 27.2. Calling it needs the 27.2 SDK and an if #available(iOS 27.2, *) around the call; not calling it changes nothing, except in the five countries, where Apple’s reference page for the older requestTrackingAuthorization(completionHandler:) says the full-page sheet appears from that call too. The margins entry reads as gated by the operating system, “on iOS 27.1 and later,” with no SDK condition stated, and the probe shows the SDK condition the note leaves out: linked against 27.0, an app keeps its 8-point margins on the 27.1 runtime; linked against 27.1, it gets zero.²⁴¹⁰

So the list splits the way September’s did. What changes when you rebuild: the margins, on a device running 27.1 or later, the first time you archive against the 27.1 SDK or the 27.2 SDK in the Xcode 27.2 RC. What changes on a user’s phone whether or not you rebuild: the operating-system changes Apple’s customer page describes, Siri AI retaining “useful context from previous Siri interactions,” “Suggestions in Messages,” Shared Albums edits, “Support for SynthID watermarking,” and FaceTime “adding a third party sign language interpreter or live captioner to a call.” None of those is an API in these notes. The StoreKit Testing fixes belong to neither list; they change SKTestSession runs in Xcode and the simulator, not a user’s phone.²⁷

The margins entry, run

The entry is one sentence of behavior, “the default layout margins for a UIView are zero,” with a version, “iOS 27.1 and later,” and no SDK condition. That shape can be tested the way the 27.0 post tested the NSURL fix: one source, several runtimes, and this time two builds. I compiled a UIKit probe twice from the same file with Xcode 27.1’s iPhoneSimulator 27.1 SDK at a minimum iOS of 18.0. The first build ran swiftc with -sdk and nothing else, and its LC_BUILD_VERSION reads sdk 27.0, because the driver recorded the macOS SDK’s version at the link step; the second ran with SDKROOT exported to the simulator SDK and reads sdk 27.1. The simulator post fell into the same trap in September and carries the warning. Both binaries ran on three simulators: iOS 18.5 (22F77) on an iPhone 16 Pro, iOS 27.2 beta (24B5084k) on an iPhone 16 Pro, and iOS 27.1 (24A94425) on an iPhone Duo, because the 27.1 runtime refuses every other device type.⁴

The last column is the entry. Linked against the 27.1 SDK and run on the 27.1 runtime, a bare UIView reports zero on every side, a subview that preserves its superview’s margins inherits the 20 points on the two edges it touches and zero on the other two where it used to get 8, and a child of a view controller’s view gets the controller’s 16-point minimum on the sides and nothing top and bottom. The view controller’s own view is unchanged: systemMinimumLayoutMargins is (0, 16, 0, 16) in every column, which is the entry’s sentence about view controllers continuing to provide their views with margins. The column beside it is the condition the entry does not state: the same source on the same runtime, stamped for the 27.0 SDK, keeps the 8-point default everywhere. A third build, stamped sdk 27.2 from the SDK in Xcode 27.2 beta, prints the same zeros on the 27.1 runtime and the same 8 points on the 27.2 beta runtime, so “27.1 or later” holds for the SDK most readers will archive against. So the change fires on a device running 27.1 or later, for an app whose binary is linked against the 27.1 SDK or later, and an app you shipped from Xcode 27 keeps the old margins on an iPhone Duo until you rebuild. Two limits. A simulator runtime is not the phone, and I have not run this on an iPhone Duo. And the first 27.2 beta runtime gives 8 points to both builds, which fits an entry that first appeared on the beta 3 page of October 5; the release runtime, 24B119, cannot be installed until Xcode 27.2 ships, so the 27.2 column is the beta’s and not the release’s.⁴

The in-window numbers for the view controller’s view itself differ by device, and the probe measures why: on the two iPhone 16 Pro simulators layoutMargins is (62, 16, 12, 16) with safeAreaInsets of (62, 0, 12, 0), and on the iPhone Duo it is (0, 16, 34, 16) with safeAreaInsets of (0, 0, 34, 0). In both cases the margins are the safe-area insets plus the (0, 16, 0, 16) minimum, the same on 18.5 as on 27.2 and in both builds.⁴

iPhone Duo shipped on an iOS 27.1 nobody else got

On Friday, October 23, Apple’s newsroom ran a photo story, “iPhone Duo arrives at Apple Store locations worldwide”: “On Friday, October 23, the highly anticipated iPhone Duo made its debut at Apple Store locations worldwide.” The day before, a developer story: “Starting this Friday, iPhone Duo users can discover amazing apps and games optimized for the first foldable iPhone,” and “Developers can easily adapt their apps for iPhone Duo using new and updated APIs in the iOS 27.1 SDK.”⁶ So the phone shipped on the date and the version Apple named on September 9, and the Duo developer post and the Duo prep post stand as written. What those posts could not say until this week is that iOS 27.1 is the phone’s alone.

The evidence is four absences and one row. Apple’s security releases page, which lists every update with a date, carries “iOS 27.1” with “iPhone Duo” in the device column, “23 Oct 2026” in the date column, and “This update has no published CVE entries,” with no link to a content page. Most rows on that page name a device family, and the few that name one product are Apple’s pattern for an update built for new hardware: “macOS Tahoe 26.3.2” for “MacBook Neo” on March 10, 2026, “watchOS 27.0.1” for “Apple Watch Series 12 and Apple Watch Ultra 4” on September 23, 2026, “watchOS 26.0.1” for “Apple Watch Ultra 3” on September 18, 2025, each with the same “no published CVE entries” note. The releases feed, which carried the 27.2 betas by build number, never carried an iOS 27.1 item. The release-notes index lists 27 and 27.2 and nothing between. Apple’s “About iOS 27 Updates” page, published October 26, has sections for iOS 27, iOS 27.0.1, and iOS 27.2 and none for 27.1, and no sentence about iPhone Duo. And on this Mac, xcrun simctl list runtimes -j reports the iOS 27.1 runtime with one supported device type, iPhone Duo, where the 27.2 beta runtime lists 62; simctl create on an iPhone 16 Pro against 27.1 fails with “Incompatible device.”¹²⁴⁵⁷

Three limits on that reading. Apple’s pages never use the word “only,” so “iPhone Duo alone” is my conclusion from the listings, not Apple’s sentence. A simulator runtime’s device list is a weak witness on its own; the visionOS runtimes on this Mac also list one device type, because there is one Vision Pro, so what counts is the comparison inside the iOS line, where the 18.x and 27.2 runtimes list 53 to 62 types and 27.1 lists one. And “never carried” rests on fetches rather than on a continuous record: a script read the feed every ten minutes from the evening of October 15 to midday today, 1,403 polls of which 20 failed to fetch, looking for a title that began “iOS 27.1 (“, and no read found one, including a copy saved at 11:28 Pacific today that still held the October 19 RC items. Press reports on launch day said the same thing in plainer words, and I cite them as press.¹¹¹

Two build numbers go with it, and Apple has published neither on a page I can cite. The iPhoneOS and iPhoneSimulator SDKs inside Xcode 27.1 (27A9275), the release since October 15, identify as iOS 27.1 build 24A94232, a lower number than the 24A94403 the September beta’s SDK carried, and the 27.1 simulator runtime is 24A94425. Press reports ten days before launch gave the same two numbers as the phone’s shipping build and its day-one update, which I note as press reporting and not as Apple’s word.⁴¹¹

Today’s second iOS 27.2 build is the loose end. The feed lists “iOS 27.2 (24B91020)” first and “iOS 27.2 (24B119)” second, both at 10:00, and Apple’s page for the first carries the title, the download link, and the release-notes link, and names no device. A separate build for the newest hardware is Apple’s pattern for a phone that launched on its own branch, and the press coverage of the day reports the two features Apple’s customer notes do not list, Apple Pencil (USB-C) support and Edge Light on iPhone Duo, as 27.2 additions for that phone. Until Apple’s page says which device runs 24B91020, the post says what the feed says: two builds, one version.¹¹¹

What it means for an app: nothing new to build against, and one number to stop waiting for. There is no 27.1 notes page coming; the 27.2 notes carry the one UIKit entry that names 27.1, and the Duo APIs the simulator post read in the 27.1 SDK are the ones to ship against. TestFlight 4.4.1, dated October 22, “includes: Support for iPhone Duo,” so the external build you send a tester on the phone installs through the store app rather than a workaround.³

What is in the security content?

The iOS 27.2 security page, “Released October 26, 2026,” lists 162 CVE-2026 identifiers and one from 2022 across 67 component headings; WebKit has 26, Kernel 15, ImageIO 11, AVEVideoEncoder and Model I/O six each. The words “exploited” and “actively” do not appear on the page. Most entries are “Available for: iPhone 11 and later, iPad Pro 12.9-inch 4th generation and later, iPad Pro 11-inch 2nd generation and later, iPad Air 4th generation and later, iPad 9th generation and later, and iPad mini 6th generation and later.” The same day’s iOS 26.7.2 and iPadOS 26.7.2 page lists 133 CVE-2026 entries and one from 2019 for the line that did not move to 27, macOS Golden Gate 27.2 lists 262 and the same 2022 entry, and Safari 27.2 lists 33.⁵

For a developer the number that matters is the one on the 27.1 row: none. A phone that shipped Friday on 27.1 and updates to 27.2 today picks up the 162 fixes with it, which is one argument for not holding a Duo test device on 27.1 to preserve a reproduction.

Is Xcode 27.2 out?

No. The release candidate, 27B48, is dated Monday, October 19 at 10:00 Pacific and is the newest Xcode item in the feed; its notes page is still titled “Xcode 27.2 RC Release Notes,” last modified October 19 at 04:56 GMT, the evening of October 18 in Cupertino, and its Overview reads “Xcode 27.2 RC 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 RC supports on-device debugging in iOS 17 and later, tvOS 17 and later, watchOS 10 and later, and visionOS. Xcode 27.2 RC requires a Mac running macOS Tahoe 26.6 or later.” App Store Connect took RC-SDK builds for the App Store from October 20, quoted in the table above, which differs from September in one respect: Xcode 27 shipped the same day as the 27.0 systems, and this time the systems shipped without their Xcode.¹³⁸

The RC page adds to the beta 3 page the 27.2 beta post read on October 14. Device Hub “contains multiple improvements,” listed as Slow Motion Animation, Simulate Shake, Simulate Fall, and Simulate Memory Pressure for simulators, a context menu for screenshots, better drag and drop for the screenshot icon, an option to hide device bezels, and an App Settings group with quit behavior, keyboard shortcuts, secure keyboard entry, hardware keyboard simulation, and a screen-capture save location (189236369). Two Device Hub Known Issues from the betas are listed fixed, the Vision Pro crash without a visionOS runtime (188313956) and the memory-warning menu item (188326513). iPhone Duo gets one fix and one new Known Issue: “Fixed: In the iPhone Duo simulator, an app using CameraCaptureAccessory can use both displays at the same time without an active camera capture session. (190155353)” and “When switching between the inner and outer display of the iPhone Duo simulator, modifier keys such as Shift and Command might stop working. (189465196)”, with “Click with the mouse on the currently visible screen” as the workaround. Instruments, Memory Gauge, and XCTest UI Automation each list one fix, the last for tests “utilizing .rotateDigitalCrown.”⁸

Two entries stand that matter for a project that targets the phone. The SDK Known Issue is unchanged: “macOS, watchOS, tvOS, and visionOS SDKs in Xcode 27.2 incorrectly report 27.1 as a valid deployment target,” and now that 27.1 is known to be an iPhone-only release, a 27.1 target on any of those four is a version that does not exist. And the Mac Catalyst entry, “Projects that use APIs specific to iOS 27.1 show compile errors when building for Mac Catalyst,” with #if !targetEnvironment(macCatalyst) as the workaround, is still open in the RC, so a Duo-aware app that also ships on the Mac keeps its conditionals.⁸

The other 27.2 systems

The macOS 27.2 Golden Gate notes have six areas: a General fix for the Xcode code-completion crash on the beta (186939138), the AppKit deprecation, “The EnablePasteboardPrivacyDeveloperPreview user default has been removed. (186955507)”, a Display Settings Known Issue, “When an external display is connected, display settings might not be restored correctly, and the display arrangement might change. (188643179)”, the clean-install Notifications issue with System Settings as the workaround, the same Shortcuts entry as iOS, and the same four StoreKit Testing entries. Four resolved, one deprecation, four known. The macOS 27 notes post carries the 27.0 release the update builds on, and the Mac this post was written on has not taken the update: it is on macOS 27.0 (26A428).⁴⁹

tvOS 27.2, visionOS 27.2, and watchOS 27.2 shipped with the same timestamp. I have not read their notes pages for this post. The feed’s older-line items are iPadOS 26.7.2 (23H128) and iOS and iPadOS 18.7.11 (22H384), and the security page adds macOS Tahoe 26.7.2, macOS Sequoia 15.8.2, tvOS 26.6.1, and Safari 27.2 for Sequoia and Tahoe.¹⁵

What I would do this week

1. If you sell in the EU, read the renamed method on Apple’s reference page before you ship a 27.2 build: requestTrackingAuthorization(preferExpandedInterface:additionalInformationAction:completionHandler:), or the async form that returns the status. A call written against the first beta’s name will not compile against a header that no longer declares it, and no SDK on this Mac declares the new one.¹⁰
2. Set the margins you depend on before you archive against the 27.1 or 27.2 SDK. A bare UIView loses its 8-point default on iOS 27.1 the first time the binary is linked against 27.1 or later, in the probe above; code that sets layoutMargins or directionalLayoutMargins explicitly is correct before and after, and a subview that should follow the view controller’s margins gets preservesSuperviewLayoutMargins = true.²⁴
3. Rerun StoreKit tests that were flaky around storefront changes or dialogsDisabled; both fixes are on a shipped page now, and the runtime that carries them arrives with Xcode 27.2.²
4. If you use Nearby Interaction in DL-TDoA mode, handle NIErrorCodeResourceUsageTimeout by starting a new session with the same configuration, which is Apple’s workaround and the only one offered.²
5. Stop waiting for iOS 27.1 notes. Build Duo work against the 27.1 SDK in Xcode 27.1 (27A9275) as the Duo prep post describes, send testers TestFlight 4.4.1, and when a bug report says “27.1,” ask for the build, since Apple has published none.³⁴
6. Keep a Duo test device on 27.1 only if you need the 27.1 reproduction; the 27.2 update carries 162 security fixes the 27.1 row does not list.⁵

FAQ

When did iOS 27.2 come out, and what build is it?

Monday, October 26, 2026, at 10:00 Pacific in Apple’s releases feed, as build 24B119 for iPhone and iPad, with a second iOS 27.2 build, 24B91020, listed in the same minute for a device the page does not name.¹

Is iOS 27.1 available for my iPhone?

No, and it never was. iOS 27.1 shipped on October 23 on iPhone Duo only: Apple’s security page lists “iPhone Duo” as its device, no release-notes page exists, the “About iOS 27 Updates” page has no 27.1 section, and the 27.1 simulator runtime accepts one device type. iOS 27.2 shipped on October 26 for “iPhone 11 and later,” the device line on Apple’s security page, which by Apple’s wording includes iPhone Duo.⁴⁵⁷

What is new for developers in iOS 27.2?

Two features and five fixes. The expanded App Tracking Transparency prompt for EU users, mandatory in five countries, with its API renamed twice during the betas to requestTrackingAuthorization(preferExpandedInterface:additionalInformationAction:completionHandler:); zero default UIView layout margins on iOS 27.1 and later; and three StoreKit Testing fixes. Seven Known Issues, two of them new since beta 4, and no deprecations.²¹⁰

Does my app need to be rebuilt for iOS 27.2?

Not to keep running. No entry is phrased as applying to apps built with the 27.2 SDK, but one behaves that way: the zero default UIView margins arrive on a 27.1 device the first time your binary is linked against the 27.1 SDK or later, by the probe above, and not before. Rebuilding with the 27.2 SDK is also what lets you call the new tracking method; that SDK is in the Xcode 27.2 RC, which App Store Connect accepts for the App Store.²³⁴¹⁰

Is Xcode 27.2 released?

Not as of the afternoon of October 26. The newest Xcode item in the feed is the October 19 release candidate, 27B48, whose notes are still titled for the RC. App Store Connect has accepted its builds since October 20.¹³⁸

Did the zero-margins change reproduce?

Yes, with a condition the entry does not state. Built against the 27.1 SDK, the probe reports zero margins for a bare UIView on the iOS 27.1 runtime running on an iPhone Duo simulator; the same source stamped for the 27.0 SDK reports 8 points there, and both builds report 8 on iOS 18.5 and on the first iOS 27.2 beta runtime. The change needs both a 27.1 device and a binary linked against 27.1 or later. A simulator is not the phone, and the 27.2 release runtime is not installed on this Mac.⁴

Where are the iOS 27.2 release notes?

On Apple’s developer documentation site under iOS & iPadOS Release Notes, the page that carried the betas, now titled “iOS & iPadOS 27.2 Release Notes” and organized by area with New Features, Resolved Issues, and Known Issues under each. The counts in this post come from that page as fetched on October 26, 2026.²

Sources