Apple has released iPadOS 27 Beta 3 to developers, continuing its work on the next major update for the iPad ahead of the upcoming public beta. Rather than introducing significant new features, this release focuses on polishing the overall experience with bug fixes, performance improvements, and updates to Apple Intelligence, Dictation, HealthKit, and the frameworks developers use to build iPad apps.
With the first public beta expected soon, iPadOS 27 Beta 3 marks another step toward a more stable release. The update also fixes several issues reported in earlier betas while giving developers access to new APIs and refinements that will shape future iPad apps.
iPadOS 27 Beta 3 Focuses on Stability
Most of the changes in Beta 3 happen behind the scenes. Apple has continued refining the system by resolving bugs affecting battery recovery, Bluetooth, Foundation Models, Game Center, StoreKit Testing, SwiftUI, and UIKit.
Developers also gain several enhancements for building iPad apps. SwiftUI introduces improvements to AsyncImage caching, document management, text selection, toolbar customization, and state handling, while UIKit adds new APIs and continues refining support for multitasking and external displays on iPad.
The update also includes localized asset packs, allowing apps to download only the language resources a user needs, reducing storage requirements.
Apple Intelligence, Dictation, and HealthKit Improvements
Apple continues improving Apple Intelligence in Beta 3 with Neural Engine optimizations that reduce loading times for large on-device AI models and improve memory reporting for developers. Apps performing AI inference in the background now require a new entitlement.
Dictation also receives an upgrade through a new on-device language model that improves recognition accuracy. The feature can be enabled by navigating to Settings > Keyboard > Dictation > Advanced Dictation Preview.
HealthKit expands with support for heart rate and cycling power zones, along with new reproductive health data types for tracking menopausal state and bleeding after menopause. Apple has also updated the Health permissions flow so users can grant apps either limited or full access to their Health history.
iPadOS 27 Beta 3 Bug Fixes
Apple has resolved a number of issues introduced in previous beta releases, including:
- Fixed an issue that could leave devices with a deeply discharged battery stuck on the red battery icon during startup.
- Fixed Channel Sounding API ranging results for both Core Bluetooth and Nearby Interaction.
- Fixed several Foundation Models runtime and compiler issues.
- Fixed Game Center’s Access Point completion handler.
- Fixed Core AI model failures when Metal API Validation was enabled.
- Fixed multiple StoreKit Testing issues involving subscriptions, refunds, pricing, and transaction reporting.
- Fixed numerous SwiftUI and UIKit stability and rendering bugs.
Known Issues in iPadOS 27 Beta 3
Apple notes that several issues remain in the latest beta.
On iPad, the tip suggesting automatic tab organization in Safari may not appear, although the feature can still be accessed manually through the tab overview menu. Safari’s tab bar may also disappear until the app is relaunched, and Safari Intelligence features might not function until their required assets finish downloading.
Apple also lists ongoing issues affecting Home Screen customization, Siri, Messages, Photos, Mail, Files, Reminders, WidgetKit, Writing Tools, and several developer frameworks. Developers working with resizable iPad apps and external displays should also review the latest UIKit and SwiftUI known issues before testing their apps.
Should You Install iPadOS 27 Beta 3?
If you’re already testing iPadOS 27, Beta 3 is a worthwhile update that delivers improved stability and addresses many issues found in earlier releases. While there are few major user-facing additions, the refinements should make day-to-day testing more reliable.
As with any developer beta, bugs and compatibility issues remain. If you depend on your iPad for everyday work or school, waiting for the public beta or a later release is still the safer choice.
