Apple released iOS 27 beta 3 to developers today, July 6, 2026. The build number is 24A5380h, and it lands roughly two weeks after beta 2.
If you have a developer account, you can grab it from Settings > General > Software Update. If you are waiting for the public beta, that is still expected in July, with the final release coming in September.
Beta 3 is not a flashy release. The user-facing changes are modest. But Apple’s developer release notes tell a different story, one about Neural Engine access, on-device AI processing, the slow death of legacy features, and the bugs Apple knows about but has not fixed yet.
I covered what changed in beta 2 in depth a couple weeks ago. This one is a different beast. Here is what Apple’s developer release notes actually say about iOS 27 beta 3.
Neural Engine Gets a Lockdown in iOS 27 Beta 3
The biggest change in the beta 3 release notes is not a flashy new feature. It is a quiet infrastructure shift.
Apple is tightening Neural Engine access. Starting in iOS 27, the system restricts background access to the Neural Engine, similar to how GPU usage has been managed for years. If your app wants to run inference on the Neural Engine while in the background, it needs a new entitlement: com.apple.developer.background-tasks.continued-processing.inference.
This matters because Apple Intelligence capable devices rely on the Neural Engine for on-device AI. Limiting background access prevents rogue processes from hammering the NPU and draining battery. It also means any developer building AI features that run in the background needs to explicitly request permission.
The release notes also say large model loading (over 1 GB) performance has improved on the Neural Engine, and Neural Engine memory usage is now attributed to the app process instead of the system, meaning you can see it in the Allocations instrument. That is a real quality-of-life improvement for anyone debugging AI model memory usage.
Dictation Gets a New On-Device Model
Apple added a toggle in Keyboard Settings labeled Advanced Dictation Preview. When enabled, Dictation runs on a new on-device model that Apple says boosts accuracy.
This is worth paying attention to. On-device Dictation means your audio never leaves the phone. Better accuracy combined with local processing is a genuine privacy win.
But there is a catch. The same release notes list a bunch of Dictation bugs that are still open:
- Voice editing commands like Change X to Y, Delete X, and Undo/Redo do not work reliably
- Formatting commands like New Line and All Caps also unreliable
- Dictating punctuation inserts both the spoken command word and the punctuation character
- Contact names are sometimes not recognized
- Extra words get inserted at the end of dictated passages
The new model is available in beta 3, but it is clearly not ready for prime time. If you rely on Dictation for serious work, beta 3 is not where you want to be.
Stricter TLS Requirements Are Coming
This one only matters if you manage Apple devices in an enterprise or school environment. And if you do, pay attention.
Starting in iOS 27, select system processes will enforce stricter network security (TLS) requirements. The affected processes are those handling MDM, DDM, Automated Device Enrollment, configuration profile installation, app installation, and software updates.
The minimum bar is TLS 1.2, with cipher suites and certificates that meet App Transport Security (ATS) requirements. If your internal servers are running older TLS configurations, those connections will break when iOS 27 ships.
Apple has a support document on preparing your network environment. If you manage Apple devices, read it before September.
AirPort Utility Is Done
Apple confirmed that AirPort Utility will no longer be available for new downloads from the App Store starting in iOS 27. If you already have the app installed, you can still re-download it, but Apple says functionality is not guaranteed on iOS 27 and later.
This is not a surprise. Apple stopped making AirPort hardware years ago. The app has been in maintenance mode for a long time. Still, if you are one of the people still running an AirPort Extreme or Time Capsule, this is your cue to modernize your home network setup.
HealthKit Adds Heart Rate Zones and Menopausal Tracking
HealthKit picked up two significant additions in beta 3.
Heart rate and cycling power zones are now available through HealthKit. Apps can read and write zone data for workouts, which is relevant if you use a cycling app, a smart trainer, or a fitness tracker that supports power meters.
The bigger addition is reproductive health tracking. HealthKit now supports tracking menopausal state (menopause, perimenopause, or none) and bleeding after menopause episodes, with severity levels from unspecified to heavy. Both types are read/write under the Reproductive Health category and require standard HealthKit authorization.
These additions continue Apple’s push into women’s health. The cycle tracking features have been expanding every year, and menopausal support closes a gap that existing health apps have been inconsistent about covering.
Playstation Access Controller Support
The PlayStation Access controller is now supported on iPadOS and iOS, not just macOS where it already worked. You can create custom input profiles in Game Controller settings and save them to your Apple device.
This is a niche addition, but for anyone who uses adaptive controllers, it matters. Apple has been steadily expanding controller support, and the Access controller is one of the better options on the market for players who need customizable inputs.
UIKit: Launch Screens Are Now Mandatory
If you are an iOS developer, this one is for you.
Apps built with the iOS 27 SDK must include a launch screen. Your Info.plist needs one of: UILaunchStoryboardName, UILaunchStoryboards, UILaunchScreen, or UILaunchScreens. Apps that do not include one will be rejected when the App Store starts accepting apps built with the 27.0 SDK.
Also worth noting: apps built with the latest SDK must adopt the scene-based lifecycle or they will fail to launch entirely. If you are still using the old app delegate lifecycle, iOS 27 is your deadline.
SwiftUI Gets @State Macro + New Document Protocols
SwiftUI picked up a batch of changes in beta 3 that developers should know about.
The @State property wrapper is now implemented as a Swift macro in Xcode 27. This eliminates the repeated initialization of @State values that happened every time the view struct re-instantiated. The old behavior meant Model() could get called dozens of times throughout a view’s lifetime. The new macro-based approach evaluates it once.
There is a source compatibility consideration. If you assign a value to @State in an initializer while also providing an initial value at declaration, the code will no longer compile. The fix is straightforward: drop the initial value at declaration if you assign it in an initializer.
The new ReadableDocument and WritableDocument protocols are also here, replacing ReferenceFileDocument for new apps. They support async reading and writing, progress reporting, and direct access to document URLs. AsyncImage now automatically caches using HTTP caching protocols. And you can use .toolbarColorScheme() to set a preferred status bar color scheme.
On Demand Resources Is Deprecated
Apple deprecated On Demand Resources and the NSBundleResourceRequest API. The replacement is Background Assets, which shipped in iOS 26 and provides a more modern approach to downloading assets on demand.
MetricKit Gets a Swift-First API
MetricKit now has a new Swift-first MetricManager API that delivers MetricReport and DiagnosticReport objects through AsyncStream. The original Objective-C APIs (MXMetricManager, MXMetricManagerSubscriber, etc.) are no longer recommended for new adoption.
New diagnostics include MemoryExceptionDiagnostic for memory limit terminations, a new MetalFrameRateMetric for Metal frame pacing insights, and CrashDiagnostic now includes a terminationCategory.
The Known Issues List Is Long
Every iOS beta has a list of known issues. Beta 3’s list is notably long and covers some serious-sounding bugs.
Some highlights:
- CarPlay audio bug: Playing Stereo music after Spatial Audio content causes silence. The workaround is to reconnect CarPlay and avoid mixing Spatial and Stereo in the same playlist.
- Siri in CarPlay: Slower responses under higher device temperatures or poor network conditions. This affects both the Siri CarPlay entry and the Nearby Interaction issue.
- Alarm from lock screen: You might not be able to stop a ringing alarm without unlocking the device. The workarounds are unlocking, saying stop the alarm, or saying stop music.
- Screen Time restrictions: May not apply to child accounts despite being configured.
- Notifications: Critical alerts will be automatically turned on for any app that requests notification permission. You must manually turn them off in Settings.
- Sleep Focus: May not automatically toggle on/off after a reboot or update until you unlock the device.
- Status bar: May appear blurred while apps are foregrounded. Workaround: reboot.
- System stability: Devices might freeze or panic when idle.
- Siri: Cannot create recurring reminders. Photo-related questions may return web results instead of ChatGPT. Some Siri voices default to legacy US voices when the device is overheated or in Low Power Mode.
- Mail: Emails might display content that does not match their subject line.
The Bottom Line
iOS 27 beta 3 is a developer beta, through and through. The user-facing changes are minor. The infrastructure changes (Neural Engine lockdown, stricter TLS, mandatory launch screens, deprecated APIs) are the real story.
If you are a developer, update and test. If you are a power user, wait for the public beta later this month. If you are a normal iPhone user, keep waiting for September.
The beta 3 release notes confirm that iOS 27 is still taking shape. Some features work. Some do not. Some are being quietly deprioritized. That is normal for July. By September, Apple will have ironed most of this out.
I will update this piece if anything significant changes in beta 4.
