Apple has released watchOS 27 Beta 3 to developers, continuing to refine the next major Apple Watch software update ahead of its public beta. While this release is primarily focused on stability, it also introduces new HealthKit capabilities, StoreKit enhancements, SwiftUI improvements, and several bug fixes across the operating system.
Compared to earlier betas, watchOS 27 Beta 3 is a smaller update that focuses on polishing the overall experience rather than adding major user-facing features. It also addresses issues affecting heart rate monitoring, Foundation Models, StoreKit Testing, and Watch Connectivity while documenting a handful of known issues that developers should be aware of.
What’s New in watchOS 27 Beta 3
The most notable addition in watchOS 27 Beta 3 is expanded support for HealthKit. Apple has added APIs for heart rate zones and cycling power zones, giving fitness and workout apps more data to build richer training experiences.
StoreKit also gains several new capabilities. The update introduces support for subscription Bundles and subscription Suites, along with new transaction types for volume purchases and additional APIs that provide more information about bundled subscriptions and Advanced Commerce purchases.
SwiftUI receives another round of improvements in Beta 3. AsyncImage now automatically caches downloaded images using standard HTTP caching, helping improve performance and reduce unnecessary network requests. Apple has also introduced a new implementation of @State that avoids repeated initialization, new APIs for customizing text input borders, improved @ContentBuilder performance, and several other enhancements for app developers.
On the system side, Apple has added new Swift APIs for file system operations, making it easier for developers to work with file metadata using native Swift instead of C-based APIs.
watchOS 27 Beta 3 Bug Fixes
Apple has resolved several issues reported in previous beta releases, including:
- Fixed an issue where using a third-party heart rate monitor could incorrectly affect background heart rate measurements and heart rate notifications.
- Fixed multiple Foundation Models runtime and compiler issues.
- Fixed several StoreKit Testing bugs involving subscriptions, refunds, transaction updates, pricing, and purchases.
- Fixed Watch Connectivity so
transferCurrentComplicationUserInfoworks correctly with WidgetKit-based complications. - Fixed several SwiftUI issues affecting file export dialogs, TabView selection behavior, layout calculations, buttons, sheets, popovers, and
@Statecompilation. - Fixed a new Swift System API conflict that could cause build errors.
Known Issues in watchOS 27 Beta 3
Apple continues to list several known issues in the latest beta.
FaceTime Audio calls from Apple Watches configured through Family Setup to devices running iOS 27 betas may fail, although incoming FaceTime calls and standard cellular calls continue to work correctly.
Users on Verizon may experience failed incoming and outgoing cellular calls if they upgraded from an earlier watchOS release directly to Beta 2. Apple also notes that Text-to-911 may not work in this scenario.
Other known issues include missing complications in the Watch app’s Face Gallery, Sleep Focus not automatically activating after restarting or updating, the Smart Stack Now Playing suggestion failing to start media playback, and the Always-On Display status bar clock occasionally failing to update. Siri may also have trouble resolving certain entity types within apps.
Should You Install watchOS 27 Beta 3?
If you’re already testing watchOS 27, Beta 3 is a worthwhile update that improves stability while introducing new HealthKit APIs and developer enhancements. Although there are few major features for everyday users, the latest beta fixes several issues that affected earlier releases and continues preparing the platform for its public launch.
As with any developer beta, bugs remain, and Apple still lists several known issues that could affect daily use. Unless you need to test apps or new APIs, waiting for the public beta is still the safer option.
