Apple released the fourth developer betas of iOS, iPadOS, macOS, watchOS and visionOS 27.2 on October 13 at 17:00 UTC. The builds are 24B5110a for iOS and iPadOS, 26B5112a for macOS, 24S5112a for watchOS and 24N5114a for visionOS. Apple’s release feed lists no new tvOS beta or Xcode release for that date.
The 27.2 release notes are cumulative. They provide a useful regression checklist, but do not establish that every listed fix arrived in beta 4. The checks below are based on Apple’s documentation, without hands-on testing.
Check the Mac development setup
Apple’s macOS notes list the Xcode code-completion crash as resolved. They still flag external-display settings that may fail to restore correctly, potentially changing the arrangement. For a development Mac, retest completion in an existing project and check the monitor layout before relying on the setup.
Clean installations may also miss notification-permission prompts for some built-in apps. Apple’s workaround is to enable affected apps manually in System Settings → Notifications. The same notes say the EnablePasteboardPrivacyDeveloperPreview default has been removed, so review any test setup that still uses it. macOS release notes
Revisit tracking prompts and simulators
The iOS and iPadOS notes record successive renames of the expanded App Tracking Transparency authorization API, ending with the requestTrackingAuthorizationPreferringExpandedInterface form. Check integrations against the current SDK rather than copying an earlier beta’s call site.
Apple also flags a permissions problem that can prevent cloning a simulator using the 27.2 runtime. Teams that clone simulators for repeatable tests should verify that workflow. The documented workaround deletes matching files inside the source simulator’s data directory; review its scope before using it.
Keep subscription edge cases covered
The StoreKit testing sections for macOS, iOS and iPadOS, watchOS and visionOS list fixes involving introductory-offer eligibility after clearing transactions, storefront updates and unwanted error dialogs during failed purchases. These are useful regression cases for apps with in-app purchases.
One important case remains open: an in-app purchase involving a subscription in a bundle can incorrectly permit unbundling instead of returning an error. Apple still lists this as a known StoreKit testing issue. Keep it visible when interpreting subscription-test results; the resolved items do not make every purchase path reliable.
