What's New in watchOS 27 Beta 7
This watchOS 27 Beta 7 release focuses on enhancing health tracking features and fixing various issues related to connectivity, calls, and app functionalities. Some changes will only be noticeable once app developers update their apps.
-
New heart rate and cycling features
HealthKit now includes support for heart rate and cycling power zones, which could enhance your workout tracking experience once app developers adopt these features.
HealthKit now supports heart rate and cycling power zones.
Apple's own words, from the HealthKit section of the notes
-
Improved network security requirements
Certain system processes now require stricter network security standards. This might affect connections if servers do not meet the new requirements.
Starting in 27.0 operating systems, select system processes now enforce stricter network security (TLS) requirements. These new requirements might cause connections to fail if the server does not meet them. The affected processes are those involved in MDM, DDM, Automated Device Enrollment, configuration profile installation, app installation, and software updates. Servers must support TLS 1.2 at minimum, using cipher suites and certificates that meet App Transport Security (ATS) requirements. For additional details on affected processes, requirements, and how to audit and diagnose failures in managed environments, please reference . For additional details on ATS and the new requirements, please reference and .
Apple's own words, from the Network Security section of the notes
-
FaceTime call issue resolved
A problem where outgoing FaceTime Audio calls from Apple Watches set up for family members might fail has been fixed.
Fixed: Outgoing FaceTime Audio calls from Apple Watches set up for family members to iOS devices running beta releases (27.0) might fail. Incoming FaceTime calls and cellular calls work correctly, as do calls to devices running iOS 26.0 or later.
Apple's own words, from the AV Conference Telephony section of the notes
-
Cellular call issues on Verizon fixed
Issues with making and receiving cellular calls on the Verizon network after upgrading or reinstalling watchOS have been resolved.
Fixed: Cellular incoming and outgoing calls might fail on Verizon network if the user upgrades from previous watchOS release to watchOS 27.0 beta 2 or performs an erase/clean install of watchOS 27.0 beta 2. Text-to-911 might also fail on Verizon network.
Apple's own words, from the Cellular section of the notes
-
Complications display issue fixed
An issue where some complications might be missing in the Watch app’s Face Gallery has been resolved.
Fixed: Some complications might be missing in the Watch app’s Face Gallery.
Apple's own words, from the Complications section of the notes
Summarised by us from watchOS 27 Beta 7 Release Notes on September 8, 2026. Each point cites the area of Apple's notes it came from, and nothing is included that Apple did not publish.
That is our plain-English reading of Apple's release notes for this build, which cover 25 areas of the system — 15 new features, 44 resolved issues, 6 known issues, 1 deprecations. Every point above traces back to an item Apple published; we translate the notes, we do not add to them. Apple's own wording, in full and unedited, follows below.
Those notes are written for developers, so they describe frameworks, APIs and fixed bugs rather than consumer features. That makes them the most precise record of what actually changed in this build — and the reason a fix you noticed may be listed under the framework responsible rather than under the app you saw it in.
App Intents2 Resolved Issues
Resolved Issues
- Fixed: AppEntity instances have a cumulative size limit of 10MB, including all child properties and their values. Your app might crash if an entity exceeds this limit, and the exception is logged.
- Fixed: The notes.appendText schema erroneously disappeared from the SDK.
AV Conference Telephony1 Resolved Issues
Resolved Issues
- Fixed: Outgoing FaceTime Audio calls from Apple Watches set up for family members to iOS devices running beta releases (27.0) might fail. Incoming FaceTime calls and cellular calls work correctly, as do calls to devices running iOS 26.0 or later.
Cellular1 Resolved Issues
Resolved Issues
- Fixed: Cellular incoming and outgoing calls might fail on Verizon network if the user upgrades from previous watchOS release to watchOS 27.0 beta 2 or performs an erase/clean install of watchOS 27.0 beta 2. Text-to-911 might also fail on Verizon network.
Communication Safety1 Resolved Issues
Resolved Issues
- Fixed: Sensitive QRCode detected as non-sensitive, preventing 3rd party developers from testing API functionality.
Complications1 Resolved Issues
Resolved Issues
- Fixed: Some complications might be missing in the Watch app’s Face Gallery.
Foundation1 Resolved Issues
Resolved Issues
- Fixed: +[NSURL URLWithString:] no longer double-encodes the % of valid percent-escape sequences when encoding other invalid characters.
Foundation Models6 Resolved Issues
Resolved Issues
- Fixed: Private Cloud Compute might not work when you use simulators.
- Fixed: Truncating transcript history in the onPrompt modifier might cause an unexpected runtime error.
- Fixed: onPrompt might not be called when applied to a Profile without instructions.
- Fixed: PrivateCloudComputeLanguageModel always uses greedy decoding.
- Fixed: Using @Generable on an enum fails to compile for watchOS.
- Fixed: Foundation Models framework cannot be imported when building for watchOS in Xcode 27 beta 2.
Health1 Resolved Issues
Resolved Issues
- When a third-party heart rate monitor is active, Apple Watch pauses background heart rate measurements and heart rate notifications (irregular rhythm, high heart rate, and low heart rate) for the duration of the session.
HealthKit1 New Features1 Resolved Issues
New Features
- HealthKit now supports heart rate and cycling power zones.
Resolved Issues
- Fixed: null unit might incorrectly convert to count and percent units.
Network Security1 New Features
New Features
- Starting in 27.0 operating systems, select system processes now enforce stricter network security (TLS) requirements. These new requirements might cause connections to fail if the server does not meet them. The affected processes are those involved in MDM, DDM, Automated Device Enrollment, configuration profile installation, app installation, and software updates. Servers must support TLS 1.2 at minimum, using cipher suites and certificates that meet App Transport Security (ATS) requirements. For additional details on affected processes, requirements, and how to audit and diagnose failures in managed environments, please reference . For additional details on ATS and the new requirements, please reference and .
Security1 Resolved Issues
Resolved Issues
- Fixed: Obtaining new certificates via ACME fails. New MDM enrollments using Managed Device Attestation fail.
Siri2 Resolved Issues4 Known Issues
Resolved Issues
- Fixed: Siri might not resolve some entity types when your app has provided only an EntityStringQuery for the entity type.
- Fixed: Siri AI might be unable to complete certain actions on Apple Watch for English users in locales outside the United States.
Known Issues
- Siri might appear to be listening when it is not after extended periods of silence while the Siri interface remains on screen.
- As of beta 5, SiriAI conversation history no longer syncs to devices running a prior beta. iCloud sync works between devices updated to beta 5. No existing conversations will be lost.
- SiriAI conversations might not sync to paired Apple Watch, failing with a “No iCloud is configured” error. Workaround: On the Watch, open Settings > Apple Account to trigger an account refresh and restores syncing.
- Apple Watch devices updated from an earlier beta might remain in a state where Siri conversation history does not sync with the paired iPhone. In most cases, the watch recovers on its own without any action. Workaround: If syncing doesn’t resume, open Settings > Apple Account on Apple Watch to trigger an account refresh.
Sleep Focus1 Resolved Issues
Resolved Issues
- Fixed: Sleep Focus may not automatically toggle on/off after a reboot or update until the user unlocks the device.
Smart Stack1 Resolved Issues
Resolved Issues
- Fixed: Tapping the Now Playing “Suggestions” widget in Smart Stack does not start playback.
Status Bar1 Resolved Issues
Resolved Issues
- Fixed: When Apple Watch is in the Always On state, the time in the status bar may not update.
StoreKit3 New Features3 Resolved Issues
New Features
- StoreKit now includes the Transaction.OwnershipType.assigned and Transaction.RevocationType.assignmentRevoked enum values to support volume purchases. Transaction query methods now additionally return transactions assigned to the Managed Apple Account.
- New Product.ProductType APIs represent subscription Bundles and subscription Suites. New APIs in Product.SubscriptionInfo.BundledSubscription let you fetch merchandising data about subscriptions contained in a Bundle. Transaction and RenewalInfo contain new fields that provide information about purchases and customer status regarding Bundles and Suites.
- partnerName and partnerId properties for Advanced Commerce API are available in and .
Resolved Issues
- Fixed: Storefront API might return incorrect metadata when running in the TestFlight environment.
- Fixed: Purchases of non-subscription In-App Purchases made using the SKTestSession.buyProduct() method might fail with an invalid product error. The billingPlanType(_:) PurchaseOption isn’t respected for subscription purchases.
- Fixed: Transactions fail to finish.
StoreKit Testing in Xcode9 Resolved Issues2 Known Issues
Resolved Issues
- Fixed: The unified app receipt is not updated after forcing a subscription expiration with SKTestSession.
- Fixed: The SKTestSession disableDialogs setting is not always respected for all system dialogs.
- Fixed: Subscription upgrades performed with the Xcode Transaction Manager are not reported in Transaction.updates.
- Fixed: The renewal behavior preference is not respected when using the purchaseDate(_:renewalBehavior:) purchase option to make purchases using SKTestSession.
- Fixed: Re-purchasing a previously refunded non-consumable fails with an already owned error when using StoreKit Testing in Xcode.
- Fixed: Using pricingTerms.commitmentInfo.price in StoreKit Testing in Xcode returns an incorrect price for monthly subscriptions with a 12-month commitment.
- Fixed: Transactions for upgraded subscriptions are immediately marked as expired when using StoreKit Testing in Xcode.
- Fixed: Purchases made with the original StoreKit API fail with an unknown error on watchOS.
- Fixed: Intro offer eligibility does not reset immediately after calling SKTestSession.clearTransactions().
Known Issues
- Changing the storefront or locale using SKTestSession doesn’t propagate through Storefront.updates.
- Failed purchases using SKTestSession might display error dialogs even when dialogsDisabled is set to true.
Swift Charts1 Resolved Issues
Resolved Issues
- Fixed: When your project has a minimum deployment target lower than 27.0, using conditionals inside a Chart closure produces the warning “Conformance of _ConditionalContent<TrueContent, FalseContent> to ChartContent is only available in ‘’ 27.0 or newer,” and the app might crash at runtime when that content is loaded.
SwiftUI8 New Features6 Resolved Issues
New Features
- AsyncImage now automatically caches downloaded images using HTTP caching protocols, allowing servers to control caching behavior via standard headers. You can customize caching for specific images using the new AsyncImage initializers that accept URLRequest with custom cachePolicy settings. Additionally, you can set a custom URLSession using the new View.asyncImageURLSession(_:) API to control how all child AsyncImage views perform data tasks.
- A @State declared with an expression as its initial value used to evaluate the expression each time the view struct re-instantiates. In the case of @State private var model = Model(), this means Model.init() gets called many times throughout the view’s lifetime. Xcode 27 introduces a new @State implementation that avoids this repeated evaluation. This new behavior back-deploys to iOS 17 aligned OSes. The new @State is implemented with a Swift macro. It is largely source compatible with the property wrapper version, with a few exceptions. If you provide an initial value at @State declaration, and also try to assign a value to it in an initializer, the initializer value is discarded. This behavior has not changed because of the macro, but some such cases no longer compile: When assigning initial value via an initializer, do not provide an initial value at the @State declaration. When all stored members of a struct are private, the compiler synthesizes a private init that can be used in an extension of the same type: The state macro disables this synthesized initializer. So the code above no longer compiles. To mitigate, assign value to members explicitly: In rare situations, the automatic inference of generic arguments of @State is less flexible with the macro implementation. Write the type with more specificity. Composing @State with other property wrappers or macros is not supported.
- You can now use the TextInputBorderShape type to customize the border shape of text input controls like TextField with the textInputBorderShape(_:) view modifier. The .squareBorder and .roundedBorder text field styles are soft deprecated — use the new .bordered text field style instead.
- In apps built with the 27.0 SDKs, a LabeledContent view used inside a Menu maps its value to the platform menu item’s subtitle.
- The @Entry macro now warns of potential issues if you store default class instances or closures in the environment. The SwiftUI Specialist skill in Xcode provides guidance for resolving these issues.
- You can now access concentricCornerRadii and concentricCornerRadii(in:) on GeometryProxy. These APIs return the corner radii that are concentric with the view’s container shape as a RectangleCornerRadii?. You can use these values to drive custom drawing or layout that responds to the container’s corners without rendering a ConcentricRectangle directly.
- @ContentBuilder type checking performance is further improved for valid code compared to Beta 1.
- The new data item or error object based alert and confirmationDialog modifiers can now be used by projects targeting iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0, and visionOS 1.0.
Resolved Issues
- Fixed: When you apply both .fileExporter(_:...) and .fileMover(_:...) modifiers to a view, some dialogs might not present correctly.
- Fixed: In apps built with the watchOS 27.0 SDK, TabView.selection updates only after the user has scrolled or rotated the Digital Crown past the 50% threshold between two pages, rather than as soon as the offset begins to change.
- Fixed: In apps built with the 27.0 SDKs, containerRelativeFrame(_:alignment:) incorrectly accounts for safe-area insets on a ScrollView’s non-scrollable axis, causing the calculated scrollable content size to be too small. For example, a view using containerRelativeFrame(.vertical) inside a horizontal ScrollView extends into vertical safe-area regions, such as the navigation bar and home indicator, because only the scrollable axis insets are applied.
- Fixed: Certain control-related view modifiers unexpectedly affect sheet and popover content. In apps built with the 27.0 SDKs, the controlSize, buttonSizing, buttonRepeatBehavior, menuIndicatorVisibility, and ButtonBorderShape environment values are now reset to their default values in sheets and popovers.
- Fixed: A Button containing both an icon and a title placed inside a List Section header or footer has incorrect spacing between its icon and title.
- Fixed: @State variable named using a raw identifier fails to compile.
System1 New Features1 Resolved Issues
New Features
- System now provides Swift APIs for the C stat, lstat, fstat, and fstatat system calls. This includes a new Stat type with initializers from FilePath, FileDescriptor, or a C string; FilePath.stat() and FileDescriptor.stat() instance methods; and supporting types (FileType, FileMode, FileFlags, UserID, GroupID, DeviceID, and Inode). See for more details.
Resolved Issues
- Fixed: Custom FilePath or FileDescriptor extensions that make unqualified calls to stat() or stat(_) (without the Darwin. qualification) might conflict with the new Swift stat() instance methods introduced in , causing build errors. See for more details.
TextKit1 New Features
New Features
- NSTextTable and its related objects and types are available to UIKit clients starting with OS 27 releases.
Watch Connectivity1 Resolved Issues
Resolved Issues
- Fixed: The WCSession.transferCurrentComplicationUserInfo method does not work with complications built using WidgetKit on watchOS.
WatchKit1 Deprecations
Deprecations
- WKExtension and WKExtensionDelegate are deprecated for apps with a minimum deployment target of watchOS 9.2 or later.
Workout Alerts and Workout Buddy1 Resolved Issues
Resolved Issues
- Fixed: When Siri AI is enabled on the paired iPhone and Apple Watch is operating in standalone, watch-only mode, Workout Alerts including Workout Buddy might fail to deliver audio announcements during an active workout.
Workout Playback1 Resolved Issues
Resolved Issues
- Fixed: Mirrored Playback might not start on iPhone when started on Apple Watch.
Source: watchOS 27 Beta 7 Release Notes, Apple Developer Documentation. Captured when this build was current — Apple replaces that page with each new beta.
What watchOS 27 Beta 7 Is
watchOS 27 Beta 7 is build 24R5358a, released on August 24, 2026. It is a pre-release build available through the developer and public beta channels, and it supersedes every earlier watchOS 27 beta.
It arrived 7 days after Beta 6 (24R5353a, August 17, 2026), against an average gap of about 11 days across this cycle. A short turnaround like this usually means a fix that could not wait for the normal two-week rhythm.
Beta 7 Build Numbers Across Every Platform
Apple ships each beta wave across its platforms on the same day, usually with different build numbers per operating system. Here is every build we recorded in this wave, taken from Apple's own release feed rather than reposted from elsewhere.
Matching build numbers between two platforms — as iOS and iPadOS almost always have — mean they are built from the same source, which is why their betas behave identically.
| Platform | Version | Build | Released |
|---|---|---|---|
| iOS 27 | 27.0 | 24A5424a | August 24, 2026 |
| iPadOS 27 | 27.0 | 24A5424a | August 24, 2026 |
| macOS 27 | 27.0 | 26A5421a | August 24, 2026 |
| tvOS 27 | 27.0 | 24J5358a | August 24, 2026 |
| visionOS 27 | 27.0 | 24M5359a | August 24, 2026 |
| watchOS 27 | 27.0 | 24R5358a | August 24, 2026 |
How to Install watchOS 27 Beta 7
There is no profile to download. Enrol your Apple Account free at beta.apple.com for the public beta or developer.apple.com for the developer channel, then open the Watch app on your iPhone → General → Software Update → Beta Updates and select the watchOS 27 channel. The build appears in Software Update like any ordinary update.
If you are already on an earlier watchOS 27 beta, this arrives as a normal update and no re-enrolment is needed. Our full watchOS 27 install guide covers the process step by step, and our device pages tell you whether your exact model qualifies.
Should You Install It?
That depends on where this build sits in the cycle and what the device is for. Early builds break third-party apps — banking and workplace apps first — and cost you a week of heavy background indexing. Later builds are progressively calmer.
Whatever you decide, make an archived backup on a computer first. A backup made on watchOS 27 cannot be restored onto the previous release, so it is the only route back with your data intact — our backup guide explains the difference, and our honest assessment covers running a beta on the phone you depend on.
What Comes After Beta 7
Beta 8 followed on August 31, 2026 as build 24R5360a, 7 days later. If you are reading this on Beta 7, that newer build is already waiting in Software Update.
Our build history tracks every watchOS build with its date and the gap before it, which is the clearest picture of how a cycle is progressing. The beta calendar guide explains the shape of the year.
Frequently Asked Questions
What's new in watchOS 27 Beta 7?
This watchOS 27 Beta 7 release focuses on enhancing health tracking features and fixing various issues related to connectivity, calls, and app functionalities. Some changes will only be noticeable once app developers update their apps. The changes Apple documented include new heart rate and cycling features, improved network security requirements, facetime call issue resolved.
What are the known issues in watchOS 27 Beta 7?
Apple lists 6 known issues for this build across 2 areas of the system, with workarounds where one exists. They are listed in full on this page under each area.
Should I install watchOS 27 Beta 7?
Not on a device you depend on. Betas break third-party apps — banking and workplace apps first — and cost battery life while the system re-indexes. If you have a spare device, or you accept restoring from scratch, it is reasonable. Back up to a computer first.
Does watchOS 27 Beta 7 fix battery drain?
Heavy battery use in the first few days after any beta update is normal and comes from background re-indexing, not from a fault. It usually settles within 48 hours. Apple's notes for this build do not single out battery life; anything genuinely fixed is listed on this page under the framework responsible.
What is the build number for watchOS 27 Beta 7?
watchOS 27 Beta 7 is build 24R5358a, released on August 24, 2026.
When was watchOS 27 Beta 7 released?
August 24, 2026, 7 days after Beta 6.
Is there a beta profile for watchOS 27 Beta 7?
No. Apple removed beta profiles in 2023. Enrol your Apple Account free at beta.apple.com or developer.apple.com and select the channel in Settings — there is no file to download.
How do I check which build I am on?
Settings → General → About, then tap the version number to reveal the build. If it reads 24R5358a you are on watchOS 27 Beta 7. Our build number guide explains how to read them.