What's New in tvOS 27 Beta 7
This release focuses on developer-facing changes, with new features primarily for app developers. Users may notice improvements once developers implement these updates in their apps.
-
Localized asset packs for apps
Apps can now use localized asset packs to reduce storage usage by delivering content based on the user's preferred languages. This change will be noticeable once developers adopt it.
You can reduce your app’s storage usage with localized asset packs. The system delivers the appropriately localized asset packs based on the user’s preferred languages.
Apple's own words, from the Background Assets section of the notes
-
HomeKit video processing
HomeKit Secure Video recordings can now be processed on-device for better video descriptions and search, but this requires an iCloud+ subscription. Users will see this feature once developers integrate it into their apps.
When Apple Intelligence in the Home app is enabled, your HomeKit Secure Video recordings are processed on-device and through Private Cloud Compute for video descriptions and search.
Apple's own words, from the HomeKit section of the notes
-
Stricter network security requirements
New stricter network security requirements may affect app connections if servers do not comply. Users might experience issues with certain apps until developers update their servers.
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
-
New StoreKit features for subscriptions
StoreKit now supports new types of subscriptions and transaction details, which will enhance how apps manage purchases. Users will notice these changes once developers implement them.
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.
Apple's own words, from the StoreKit section of the notes
-
AsyncImage caching improvements
AsyncImage can now automatically cache images, which may lead to faster loading times in apps that use this feature. Users will benefit from this once developers adopt the new caching methods.
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.
Apple's own words, from the SwiftUI section of the notes
Summarised by us from tvOS 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 24 areas of the system — 21 new features, 36 resolved issues, 2 known issues, 3 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 Intents1 Resolved Issues
Resolved Issues
- Fixed: The notes.appendText schema erroneously disappeared from the SDK.
Apple TV1 Resolved Issues
Resolved Issues
- Fixed: When launching the Apple TV app, the sidebar focus highlight might briefly appear flat on the right side.
AVKit Video Playback1 Resolved Issues
Resolved Issues
- Fixed: When a video is muted or unmuted during playback, subtitles may not be automatically enabled or disabled as expected. The subtitles-on-mute logic has not yet been updated to account for the new system behavior.
Background Assets1 New Features
New Features
- You can reduce your app’s storage usage with localized asset packs. The system delivers the appropriately localized asset packs based on the user’s preferred languages.
Foundation1 Resolved Issues
Resolved Issues
- Fixed: +[NSURL URLWithString:] no longer double-encodes the % of valid percent-escape sequences when encoding other invalid characters.
Game Center1 Resolved Issues
Resolved Issues
- Fixed: When you trigger the Access Point, its completion handler is never invoked.
HomeKit2 New Features
New Features
- When Apple Intelligence in the Home app is enabled, your HomeKit Secure Video recordings are processed on-device and through Private Cloud Compute for video descriptions and search.
- Apple Intelligence for Home requires an iCloud+ subscription starting at 2TB.
Metal2 Resolved Issues
Resolved Issues
- Fixed: When you use a sampler to read from a texture with clamp-to-edge addressing mode, the result might be clamped to zero.
- Fixed: On devices in the Apple 10 GPU family, using a sampler to read from a texture with clamp-to-edge addressing mode might produce results that are clamped to zero.
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 .
On Demand Resources1 Deprecations
Deprecations
- On Demand Resources and the NSBundleResourceRequest API are deprecated. Use Background Assets instead.
PhotoKit1 Resolved Issues1 Deprecations
Resolved Issues
- Fixed: The addedDate property on PHAsset might return nil even though it’s marked as non-nullable.
Deprecations
- The originalFilename property on PHAssetResource is incorrectly marked as non-nullable, which misrepresents the property value; a new, nullable filename property is available as a replacement.
RealityKit3 Resolved Issues
Resolved Issues
- Fixed: Some MaterialX 1.39 nodes are not supported.
- Fixed: ComputeGraphComponents stored in a Reality file do not render when loaded.
- Fixed: When OpacityComponent is applied to an entity with opaque materials, RealityRenderer renders the opaque materials with transparency, revealing interior surfaces. Only the frontmost surface should appear with partial transparency.
Security1 Resolved Issues
Resolved Issues
- Fixed: Obtaining new certificates via ACME fails. New MDM enrollments using Managed Device Attestation fail.
ShaderGraph1 Resolved Issues
Resolved Issues
- Fixed: The realitykit_hair_surfaceshader node does not support DiffuseLightProbeGroupComponent. Materials built with this node might not respond to diffuse light probe group lighting.
Siri1 Resolved Issues
Resolved Issues
- Fixed: Siri might not resolve some entity types when your app has provided only an EntityStringQuery for the entity type.
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 Xcode8 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: 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.
SwiftUI9 New Features7 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.
- The TabsPickerStyle style is now available for pickers that represent tab-based navigation and content selection. This style is similar to the .segmented style, but VoiceOver reads it as “tabs,” and on macOS it has a distinct visual appearance that distinguishes it from pickers that represent value selection — for example, a text alignment picker in an inspector.
- 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 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: Menu labels cannot contain controls, views with gestures, or view representables with gesture recognizers.
- Fixed: Buttons on tvOS no longer automatically use the accent color from an app’s asset catalog as a label tint color when building against the tvOS 27 SDK.
- 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.
UIKit1 New Features1 Deprecations
New Features
- When linked on iOS 27, tvOS 27, macCatalyst 27, or visionOS 27 SDKs, you can use UIScene.extendStateRestoration and UIScene.completeStateRestoration to extend state restoration for UIScene.ActivationState.background to UIScene.ActivationState.foreground lifecycle transitions.
Deprecations
- Apps built with the latest SDK must adopt the scene-based life cycle or they fail to launch. For migration guidance, see .
USDKit2 Resolved Issues
Resolved Issues
- Fixed: Some types of USD attributes cannot be read or modified.
- Fixed: Array, vector, matrix, and quaternion types cannot be authored using USDKit.
VideoToolbox2 New Features
New Features
- VTLowLatencySuperResolutionScalerConfiguration now supports a 1.5x scale factor. Call +supportedScaleFactorsForFrameWidth:frameHeight: to discover the scale factors available for your source dimensions.
- VTLowLatencyFrameInterpolationConfiguration now supports arbitrary source dimensions up to 1080p.
Source: tvOS 27 Beta 7 Release Notes, Apple Developer Documentation. Captured when this build was current — Apple replaces that page with each new beta.
What tvOS 27 Beta 7 Is
tvOS 27 Beta 7 is build 24J5358a, released on August 24, 2026. It is a pre-release build available through the developer and public beta channels, and it supersedes every earlier tvOS 27 beta.
It arrived 7 days after Beta 6 (24J5353b, 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 tvOS 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 Settings → System → Software Updates → Beta Updates on the Apple TV and select the tvOS 27 channel. The build appears in Software Update like any ordinary update.
If you are already on an earlier tvOS 27 beta, this arrives as a normal update and no re-enrolment is needed. Our full tvOS 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 tvOS 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 24J5360a, 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 tvOS 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 tvOS 27 Beta 7?
This release focuses on developer-facing changes, with new features primarily for app developers. Users may notice improvements once developers implement these updates in their apps. The changes Apple documented include localized asset packs for apps, homekit video processing, stricter network security requirements.
What are the known issues in tvOS 27 Beta 7?
Apple lists 2 known issues for this build across 1 areas of the system, with workarounds where one exists. They are listed in full on this page under each area.
Should I install tvOS 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 tvOS 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 tvOS 27 Beta 7?
tvOS 27 Beta 7 is build 24J5358a, released on August 24, 2026.
When was tvOS 27 Beta 7 released?
August 24, 2026, 7 days after Beta 6.
Is there a beta profile for tvOS 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 24J5358a you are on tvOS 27 Beta 7. Our build number guide explains how to read them.