iOS 27.2: What’s New, Known Issues & Fixes

What’s New

App Tracking Transparency — Expanded EU Prompts

• Alternative expanded prompt — ATT now supports a larger, more detailed authorization dialog for users in the European Union. The expanded interface is required for users in France, Germany, Italy, Poland, and Romania. (179504171)
• Yearly reprompting — Apps can re-request tracking authorization once per year for EU users, aligning with regional guidance.
• Why it matters — If your app uses AppTrackingTransparency, you must adopt the new API (see Resolved Issues for the final method names) and test the expanded flow in those five countries. Non-EU users continue to see the standard prompt.

UIKit — Zero Default Layout Margins

• On iOS 27.1 and later, UIView default layout margins are zero. A view controller still supplies systemMinimumLayoutMargins that vary by presentation context (e.g., compact vs. regular width, modal vs. push).
• To inherit those system margins in a subview, set preservesSuperviewLayoutMargins = true on the subview. (186294594)
• Why it matters — Existing layouts that relied on the old 8/16/20 pt default margins may shift. Audit Auto Layout constraints and margin-dependent spacing, especially in custom container view controllers.

Known Issues and Workarounds

Health — Personalized Summaries May Not Generate

• What breaks: The Insights tab may fail to produce personalized summaries. (186964423)
• Workaround: None listed in the release notes. Monitor the Insights tab after subsequent betas.

Health — Redesigned App Temporarily Removed

• What breaks: The redesigned Health app that appeared in the previous beta is not included in iOS 27.2. Data from the earlier beta remains on device and is viewable in Settings. The redesign will return in a future beta. (188843443)
• Workaround: Access historical Health data via Settings → Health. Do not delete the app or its data expecting the redesign to persist.

Nearby Interaction — DL-TDoA Session Resource Timeout

• What breaks: An NISession using a DL-TDoA configuration in a foreground app can be invalidated unexpectedly with NIErrorCodeResourceUsageTimeout. (189664070)
• Workaround: Create and run a new NISession with the same DL-TDoA configuration.

Quest Lab Appointments — Update Timing

• What breaks: Updating iOS before receiving lab results may interfere with appointment data. (184530996)
• Workaround: Wait to update until results arrive. Results are also available under Browse → Lab Results in the Health app.

Shortcuts — “Describe a Shortcut” Failure

• What breaks: The “Describe a Shortcut” action may fail with the alert “Something went wrong. Try again later.” (187499433)
• Workaround: None listed. Retry later or avoid the action in production shortcuts until fixed.

Simulator — Cloning Fails on Runtime 27.2

• What breaks: Cloning a simulator device running the 27.2 runtime can fail due to incorrect file permissions. (188407822, FB24939277)
• Workaround: Delete the problematic sandbox files before cloning:
  bash
find ~/Library/Developer/CoreSimulator/Devices/<SOURCE_UDID>/data \
-name '*.sb-????????-??????' -delete
  Replace <SOURCE_UDID> with the UDID of the device you are cloning.

StoreKit Testing — Subscription Bundle Unbundling

• What breaks: Purchasing a subscription that belongs to a subscription bundle incorrectly allows the user to unbundle instead of throwing an error. (186018916)
• Workaround: None listed. Validate bundle purchase logic server-side and test with production StoreKit until resolved.

Resolved Issues Worth Knowing

• ATT API renamed (Swift): requestTrackingAuthorization(usingExpandedInterface:additionalInformationAction:completionHandler:) → requestTrackingAuthorization(preferExpandedInterface:additionalInformationAction:completionHandler:). (187149729)
• ATT API renamed (Objective‑C): requestTrackingAuthorizationPreferExpandedInterface:... → requestTrackingAuthorizationPreferringExpandedInterface:.... (187610745)
• StoreKit Test — Intro offer eligibility reset: SKTestSession.clearTransactions() now immediately resets introductory offer eligibility. (183933307, FB24137836)
• StoreKit Test — Storefront/locale propagation: Changing storefront or locale via SKTestSession now correctly propagates through Storefront.updates. (184155259)
• StoreKit Test — Silent failed purchases: Failed purchases no longer display error dialogs when dialogsDisabled == true. (184255116)

Should You Update?

Update now if:

• You need to test the expanded ATT prompt for EU compliance in the five mandated countries.
• You rely on StoreKit Testing in Xcode and want the intro-offer, storefront, and silent-failure fixes.
• You are adapting layouts for the zero default UIView margins change and want real-device verification.

Wait if:

• Your app depends on Nearby Interaction DL-TDoA sessions — the resource timeout can break ranging workflows.
• You use Simulator device cloning heavily in CI — the permission bug blocks cloning until the workaround is scripted.
• You ship Shortcuts that use “Describe a Shortcut” — the intermittent failure may confuse users.
• You participate in Quest lab studies — update only after results are delivered.

Xcode project checks:

• Search for the old ATT method names (usingExpandedInterface, PreferExpandedInterface) and migrate to the new preferExpandedInterface / PreferringExpandedInterface variants.
• Verify Auto Layout constraints that assume non-zero default margins; add preservesSuperviewLayoutMargins = true where system margins should flow to subviews.
• Run StoreKit test suites against the 27.2 SDK to confirm intro-offer reset and storefront propagation behave as expected.

FAQ

Does the expanded ATT prompt apply to all EU countries?

No. The release notes specify France, Germany, Italy, Poland, and Romania as the countries where the alternative expanded prompt is required. Other EU countries may see the standard prompt unless you explicitly opt into the expanded interface.

How do I migrate my ATT authorization call to the new API?

Replace the deprecated method with requestTrackingAuthorization(preferExpandedInterface:additionalInformationAction:completionHandler:) (Swift) or requestTrackingAuthorizationPreferringExpandedInterface:additionalInformationAction:completionHandler: (Objective‑C). The parameter semantics are unchanged; only the selector name differs.

Will the Simulator cloning workaround persist across Xcode restarts?

Yes. The find … -delete command removes the offending sandbox files once. After deletion, cloning the same source device should succeed until new sandbox files with the problematic permissions are created. Add the command to your CI pre-clone step for reliability.