What's New in visionOS 27 Beta 7
This beta release of visionOS 27 brings new features and fixes, particularly enhancing Siri's interaction and improving app storage management. Some changes will only be noticeable once app developers update their apps.
-
Activate Siri with a glance
You can now activate Siri by simply looking at the Siri icon and speaking, offering an alternative to voice commands like 'Hey Siri'.
You can now activate Siri by looking at the Siri “orb” and speaking, as an alternative to using “Hey Siri” or “Siri”. This feature is enabled in Beta 2.
Apple's own words, from the Siri section of the notes
-
Localized app storage management
Apps can now use localized asset packs to reduce storage usage, delivering content based on your preferred language settings.
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
-
Stricter network security
Some system processes now require stricter network security standards, which may affect connections if servers don't meet these 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
-
Siri setup improvements
The App Clips navigation button no longer appears in Siri settings on visionOS, as App Clips are not supported.
Fixed: The App Clips navigation button appears in Siri settings, even though the App Clips feature is not supported on visionOS.
Apple's own words, from the Siri Setup section of the notes
-
Siri message sending issue fixed
A problem where messages might not send after tapping the send button in Siri's message confirmation has been resolved.
Fixed: When you tap the Send button in the Siri message confirmation flow, the message might fail to send.
Apple's own words, from the Siri section of the notes
Summarised by us from visionOS 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 53 areas of the system — 28 new features, 112 resolved issues, 14 known issues, 6 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 New Features3 Resolved Issues1 Known Issues1 Deprecations
New Features
- You can now pass a name parameter of type AttributedString to the notes.createNote and notes.updateNote schemas.
Resolved Issues
- Fixed: Requests that should result in an app’s reminders.updateReminder-conforming intent to be called might fail with “ cannot be used for this action right now.”
- 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.
Known Issues
- Existing entities that conformed to @AppEntity(schema: .photos.asset) in prior releases might no longer compile in the 27 SDKs because new properties were added to the schema in this release. Workaround: To continue conforming to the schema, adopt the additional properties and move the code behind an availability check.
Deprecations
- The calendar.deleteEvents schema has been renamed to calendar.deleteEvent.
Apple Intelligence Report1 Resolved Issues
Resolved Issues
- Fixed: When you view Apple Intelligence Report entries for Home Intelligence, some data that was sent to Private Cloud Compute won’t appear in the report.
ARKit2 Resolved Issues
Resolved Issues
- Fixed: For room anchors delivered by the RoomTrackingProvider Swift API, RoomAnchor.planeAnchorIDs and RoomAnchor.meshAnchorIDs are always empty. Likewise, for the room_tracking.h C API, ar_room_anchor_get_plane_anchor_identifiers and ar_room_anchor_get_mesh_anchor_identifiers always return an empty list of identifiers.
- Fixed: Due to a bug fix for ARKit Object Tracking, callers of the C API functions for loading reference objects (ar_reference_object_load_from_url, ar_reference_object_load_with_name, and similar) must now retain the reference objects and errors returned by the completion handlers that client code passes to these functions, in contexts where ARC is not enabled. Note, ar_retain must be called in the completion handler for reference objects, and also errors (if there is a desire to hold onto these items beyond the scope of the completion handler). Otherwise, the items will be invalid to use after the completion handler finishes execution.
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.
Bluetooth1 Known Issues
Known Issues
- Spatial accessory tracking might not initialize when first paired via Bluetooth. Workaround: Turn the accessory off and then on, or turn Bluetooth off and on.
Communication Safety1 Resolved Issues
Resolved Issues
- Fixed: Sensitive QRCode detected as non-sensitive, preventing 3rd party developers from testing API functionality.
Compositor Services1 Resolved Issues
Resolved Issues
- Fixed: RemoteImmersiveSpace might be unable to discover the remote device, causing immersive content delivered to Apple Vision Pro to fail to display.
Eye Setup1 Known Issues
Known Issues
- You might experience a degradation in eye tracking quality after performing Eye Setup in visionOS 27.0 Beta 1 through Beta 4. Workaround: After updating to visionOS 27.0 Beta 5 or later, .
EyeSight1 Resolved Issues
Resolved Issues
- Fixed: The EyeSight privacy indicator animation for screen capture only appears during your first Siri query after you restart your device.
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: When using the on-device Apple Foundation Model for both tool calling and guided generation, some prompts might cause the model to call tools excessively.
- Fixed: @Generable on an enum produces a deprecation warning about GenerationError that cannot be silenced.
- 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.
Foveated Streaming1 Resolved Issues
Resolved Issues
- Fixed: FoveatedStreamingProvider app extensions cannot access the microphone.
Freeform1 Resolved Issues
Resolved Issues
- Fixed: When a Freeform board is curved, the back button might become unresponsive after you exit preview mode for a spatial photo, spatial video, or USDZ file.
Gaussian Splats1 Resolved Issues
Resolved Issues
- Fixed: When 3DGS content rendered by a GaussianSplatComponent is moved offscreen and then returns to the visible area, some splats might be missing or truncated. Camera or asset movement can restore rendering.
Genmoji1 Resolved Issues
Resolved Issues
- Fixed: The Genmoji or Image Playground panel might appear blank when invoked from Safari or Freeform.
Hand UI1 Resolved Issues
Resolved Issues
- Fixed: The battery percentage that appears in the status bar when you raise your hand and flip it over might be inconsistent with the percentage displayed in Control Center.
HealthKit1 Resolved Issues
Resolved Issues
- Fixed: null unit might incorrectly convert to count and percent units.
Image Playground1 Resolved Issues
Resolved Issues
- Fixed: In the Image Playground photo picker, the All and Suggested tabs are missing, which might limit the number of photos available for you to choose from.
Mac Virtual Display1 Resolved Issues
Resolved Issues
- Fixed: When donning the Apple Vision Pro it may sometimes disconnect instead of resuming the session.
Mail1 Resolved Issues
Resolved Issues
- Fixed: Emails might display content that doesn’t match their subject line.
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.
Persona1 Resolved Issues
Resolved Issues
- Fixed: Spatial Personas might appear laggy during High Quality Recording.
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.
Photos1 Known Issues
Known Issues
- Toggling between 2D and Spatial views of a large panorama image (>300Mb) might cause the Photos application to unexpectedly quit. Workaround: Convert the asset to JPEG or HEIC before importing it into the photos library.
Quick Look5 Resolved Issues1 Known Issues
Resolved Issues
- Fixed: Buttons in the annotation window might lose focus and become unresponsive on the first pinch.
- Fixed: When in annotation mode, annotations placed inside an object or within the bounding box of a convex object might not be selectable.
- Fixed: Annotation text might become blank, preventing you from creating, selecting, or deleting additional annotations.
- Fixed: In annotation mode, annotations don’t respond to direct touch input and flicker when directly touched.
- Fixed: In annotation mode, the Delete button sometimes switches the annotation to the editing UI.
Known Issues
- When at an interior Viewpoint in a USD preview, using drag gestures to move the scene can cause a severe jump of the asset position. Workaround: Apply the gesture slowly, avoiding a quick hand motion. Reset the positioning by choosing the desired Viewpoint again.
Reality Composer Pro Preview on visionOS1 Resolved Issues
Resolved Issues
- Reality Composer Pro Preview, which lets you preview your content on visionOS in real time directly from your Mac, is now available. For more information on the Reality Composer Pro macOS app, see .
RealityKit15 Resolved Issues
Resolved Issues
- Fixed: The .highlight hover effect style highlights the entire RealityKit entity hierarchy during direct interactions, rather than only the entity being targeted.
- Fixed: Soft Shadows and Spotlight Shadow Quality do not work in visionOS Simulator because the feature relies on the clustering system, which is disabled due to restricted tier 2 argument buffer issues.
- Fixed: Some MaterialX 1.39 nodes are not supported.
- Fixed: Content in a portal incorrectly receives outside environment probe lighting contribution.
- RealityRenderer’s isToneMappingEnabled property enables and disables tone mapping if apps are rebuilt with the 27.0 SDK. Apps built with earlier versions of the SDK don’t see a behavior change.
- Fixed: ComputeGraphComponents stored in a Reality file do not render when loaded.
- Fixed: The behavior tree’s SetTree node might not reset the status of nodes belonging to the intended tree when you enter that tree for a second time. Additionally, if the SetTree node has adjacent children to its right, the adjacent children might process before the new tree is set. To prevent adjacent children from processing early, ensure the SetTree node is the rightmost node in its subtree.
- Fixed: Skinning animation or high subdivision level on complex geometry can cause excessive memory growth and may cause the app to be terminated due to high memory usage.
- Fixed: Opaque ShaderGraph materials appear darker than Physically Based Materials when lit by dynamic lights.
- 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.
- Fixed: Shadow rendering memory is not counted against each application’s memory limit, which might prevent apps from consistently using up to 8 shadowed directional and spot lights depending on what other apps are running.
- Fixed: Specular highlights in the PBR shading model do not fade out correctly at low specular values. A visible specular effect persists even when the specular parameter is set to 0, causing materials with zero specular to appear reflective instead of non-reflective.
- To use primitive restart with triangleStrip and lineStrips, set LowLevelMesh.Descriptor.allowsPrimitiveRestart = true.
- Fixed: Subtitles might become clipped in Multiview when resizing tiles in Multiview in TV app.
- Fixed: Shaders using the new RealityKit shader node name of ND_realitykit_pbr_surfaceshader_2_0 will fail to load in Quick Look or with USDKit.
Screen Recording2 Resolved Issues
Resolved Issues
- Fixed: With High Quality Recording enabled, capturing a High Quality recording while the device is warm may fail silently. No recording is saved and no error or feedback is shown.
- Fixed: When you switch between High Quality Recording and Standard Recording in Screen Recording settings, the recording subsystem may enter an unrecoverable state; subsequent screen recordings from Control Center might not start.
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.
Shortcuts1 Resolved Issues2 Known Issues
Resolved Issues
- Fixed: The Use Model action might fail to run when using the On-Device option for some output types.
Known Issues
- If an app intent uses Duration or LPLinkMetadata, creating a shortcut with that intent and then attempting to edit it with “Describe a change” might fail. Workaround: If the model discards the action, press “Undo” to recover the unsupported intent.
- When an app intent defines a UnionValue parameter with two number-related types (for example, both Int and Double), the number option appears twice in the parameter picker menu and shows as double-selected. Workaround: Define only one number-related type in the UnionValue parameter (for example, use only Int or only Double, not both).
Siri1 New Features18 Resolved Issues3 Known Issues
New Features
- You can now activate Siri by looking at the Siri “orb” and speaking, as an alternative to using “Hey Siri” or “Siri”. This feature is enabled in Beta 2.
Resolved Issues
- Fixed: Siri ignores custom values for navigation preferences, transport, and incident types in apps that use maps.startNavigation or maps.reportIncident intent schemas.
- Fixed: If you select the Ask Siri button in context menus or the text edit bar multiple times, multiple instances of Siri might appear and overlap with each other.
- Fixed: On visionOS, when Type to Siri is selected, dragging and dropping an image to Siri might not add the image to the Ask Siri input field.
- Fixed: When you enable Guest User Mode on Apple Vision Pro, Siri becomes unavailable.
- Fixed: When you ask Siri to send a message to a contact that doesn’t exist on your device, Siri might draft a message to an unrelated contact.
- Fixed: Siri might not resolve some entity types when your app has provided only an EntityStringQuery for the entity type.
- Fixed: Asking Siri to call short phone numbers, such as “Call 17”, might fail.
- Fixed: Disabling Siri might not delete your Siri and Dictation interaction history from your device.
- Fixed: Siri might not find app-specific contacts that are only indexed in Spotlight and do not appear in the Contacts app.
- Fixed: When you use ChatGPT with Apple Intelligence, some responses used in follow-up queries or when you resume a chat might be logged by Apple.
- Fixed: When you tap the Send button in the Siri message confirmation flow, the message might fail to send.
- Fixed: Asking Siri to generate images will present the images in a UI that is not scrollable.
- Fixed: When the Siri app chat canvas is resized to a narrow width in text entry mode, the thumbs up and thumbs down feedback buttons might be obscured by the text input platter.
- Fixed: The search text field maintains keyboard focus after returning from searching in a list using the back button.
- Fixed: Siri “orb” and UI does not correctly follow the system breakthrough behavior when near another window.
- Fixed: Conversation cards might disappear after you return from a conversation view using the back button.
- Fixed: If you pin the Siri “orb” and then reboot the device, saying “Hey Siri” might summon two “orbs”.
- Fixed: Tapping an inactive Siri “orb” or the microphone button in the Siri app might not turn on Siri.
Known Issues
- When you ask Siri for Maps information, the response snippets might appear incomplete or display formatting issues. Workaround: Ask Siri to repeat the information, or open Maps directly for complete details.
- Siri commands for Environments aren’t working. Workaround: Use gaze and pinch to open environments from the Home View.
- 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.
Siri Setup1 Resolved Issues
Resolved Issues
- Fixed: The App Clips navigation button appears in Siri settings, even though the App Clips feature is not supported on visionOS.
Spatial Accessories1 Resolved Issues
Resolved Issues
- Fixed: During use, Spatial Accessories - such as the Logitech Muse stylus or PSVR2 controllers - might stop registering inputs or being tracked.
Spatial Gallery1 Resolved Issues
Resolved Issues
- Fixed: Spatial Gallery may freeze when loading panoramas.
Spatial Preview1 Resolved Issues
Resolved Issues
- Fixed: Some large 3D models with poor mesh connectivity of approximately 750,000 to 3.75 million triangles might not appear when previewing on Apple Vision Pro.
Spatial Web1 Resolved Issues
Resolved Issues
- Fixed: WebXR might not render when you use Simulator.
Status Bar1 Known Issues
Known Issues
- Battery percentage might not be up-to-date in the status bar. Workaround: Open Control Center to update the battery percentage.
StoreKit4 New Features5 Resolved Issues
New Features
- Offer code redemption APIs now return a VerificationResult when redemption completes. If a redemption succeeds, your app receives a VerificationResult that contains a Transaction object. If a redemption fails, your app receives an error that describes what caused the redemption to fail.
- 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: The refund request, offer code redemption, and manage subscriptions sheets might fail to present in TestFlight.
- Fixed: Displaying the offer code sheet or the manage subscription sheet consecutively might cause the app to hang when using StoreKit Testing in Xcode.
- 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 Xcode10 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: StoreKit UI actions (manage subscriptions, redeem offer code, and refund request) don’t perform the desired action on visionOS when using StoreKit Testing in Xcode.
- 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 fail on visionOS when initiated from offer code redemption or from the manage subscriptions sheet.
- 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.
SwiftData1 Resolved Issues
Resolved Issues
- Fixed: You might experience a deadlock for @Query when saving a ModelContext on a background actor while scheduling new async tasks for a ModelActor.
SwiftUI15 New Features8 Resolved Issues1 Deprecations
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.
- In apps built with the 27.0 SDKs, the new ReadableDocument and WritableDocument protocols support asynchronous reading and writing, progress reporting, and direct access to document URLs. New DocumentGroup initializers that adopt these protocols let you disable document creation for editing-only apps and present custom UI before any document is opened. The initializers expose an Observable URLDocumentConfiguration and integrate with Swift concurrency and the Observation framework. New applications should prefer ReadableDocument and WritableDocument over ReferenceFileDocument, which remains available.
- 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.
- You can now use the Document protocol for representing documents in DocumentGroup. This protocol combines ReadableDocument and WritableDocument for common read-and-write cases. Use Document instead of ReferenceFileDocument and FileDocument, which are now deprecated.
- @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.
- In macOS apps built with the macOS 27 SDK, the action retrieved from the \.newDocument environment value accepts an in-memory ReadableDocument produced by an autoclosure. SwiftUI presents a new document window populated with the supplied instance, instead of invoking the document group’s default factory. Use this to implement “New from Template” commands and similar flows.
- A new fileExporter(isPresented:documents:contentTypes:onCompletion:onCancellation:) modifier exports a collection of values that conform to WritableDocument whose Writer.Destination is URL. The system presents a single export dialog, writes each document to the chosen destination, and reports the resulting URLs through onCompletion.
- The makeFileWrapper closure of FileWrapperDocumentWriter now receives a second argument, previous: FileWrapper?, holding the FileWrapper from the document’s most recent read or write when one is available. Package documents can mutate previous in place and return it so that FileWrapper only writes children whose contents changed, avoiding rewriting an entire package on every save. Documents stored as a single file can ignore the second argument and return a fresh FileWrapper as before. Existing call sites must update their closures to accept the new parameter.
- DocumentReader.Source and DocumentWriter.Destination now default to URL. Conforming types that read from or write to a file URL no longer need to declare typealias Source = URL or typealias Destination = URL.
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: @State variable named using a raw identifier fails to compile.
- The read(from:progress:) and write(content:to:previous:progress:) requirements of DocumentReader and DocumentWriter are declared with @concurrent instead of nonisolated. With approachable-concurrency defaults that infer MainActor isolation, an unannotated nonisolated async method runs on the main actor, defeating the intent of off-main reading and writing. Conforming types that previously used nonisolated should switch to @concurrent to match.
- The makeDocument: and makeReadableDocument: closures passed to DocumentGroup initializers are now @MainActor-isolated. SwiftUI invokes these factories on the main actor when constructing a document instance, allowing the closure body to access main-actor state — including the supplied URLDocumentConfiguration — without hopping isolation domains.
- URLDocumentConfiguration is a @MainActor-isolated @Observable reference type and no longer conforms to Sendable. Code that captured a configuration in a Sendable closure or stored it in a Sendable value should drop the constraint and access the configuration on the main actor.
Deprecations
- The FileDocument protocol is deprecated. Use ReadableDocument for read-only documents or Document for documents that support reading and writing.
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.
TestFlight1 Known Issues
Known Issues
- Apps installed via TestFlight may launch into a blank window with no content. The TestFlight “What to Test” introductory screen may not appear before the app, or the app’s window may render empty. Workaround: Close the blank window and relaunch the app from the Home View. The launch typically succeeds within 1–3 attempts. If an app remains stuck, force-quit it (long-press the Digital Crown) and launch again from the Home View.
TextKit1 New Features
New Features
- NSTextTable and its related objects and types are available to UIKit clients starting with OS 27 releases.
UIKit1 New Features2 Resolved Issues1 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.
Resolved Issues
- Fixed: -[UIApplication supportedInterfaceOrientationsForWindow:] and -[UIApplicationDelegate application:supportedInterfaceOrientationsForWindow:] are marked as unavailable in the visionOS SDK rather than deprecated.
- Fixed: Views hosted in a UIHostingController and positioned using Auto Layout might have broken layout due to an overly aggressive fix for a layout feedback loop.
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 Issues1 Deprecations
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.
Deprecations
- Meshes compressed using the USDKit export API or usdcrush tool in Beta 1 cannot be decoded by Beta 2, and meshes from Beta 2 cannot be decoded by Beta 1.
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.
WebKit3 Resolved Issues
Resolved Issues
- Fixed: Some models embedded in web pages might render off-center within the portal or might be hidden by portal edges.
- Fixed: 3D models hosted in <model> HTML elements might appear darker than expected when the system environment is set to Dark Mode.
- Fixed: The <model> element renders differently across iOS, macOS and visionOS, primarily as brightness/darkening differences and some color temperature and specular highlight discrepancies.
Xcode1 Resolved Issues
Resolved Issues
- Fixed: When you use the Debug View Hierarchy tool (View Debugger) to inspect an app that presents RealityKit content with SwiftUI RealityView, the RealityKit scene appears empty: the RealityView’s entities are missing from the captured hierarchy and the RealityKit debugger shows no content. This affects apps running on visionOS, the iOS Simulator, and macOS. Debugging of non-RealityKit content (UIKit, AppKit, and 2D SwiftUI views) is unaffected. The content is still present in your app and renders correctly at runtime; only its visibility to the View Debugger is affected, due to a change in how RealityKit exposes RealityView-hosted entities to the debugging APIs the View Debugger relies on.
Source: visionOS 27 Beta 7 Release Notes, Apple Developer Documentation. Captured when this build was current — Apple replaces that page with each new beta.
What visionOS 27 Beta 7 Is
visionOS 27 Beta 7 is build 24M5359a, released on August 24, 2026. It is a pre-release build available through the developer and public beta channels, and it supersedes every earlier visionOS 27 beta.
It arrived 7 days after Beta 6 (24M5355a, 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 visionOS 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 → General → Software Update → Beta Updates and select the visionOS 27 channel. The build appears in Software Update like any ordinary update.
If you are already on an earlier visionOS 27 beta, this arrives as a normal update and no re-enrolment is needed. Our full visionOS 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 visionOS 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 24M5361a, 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 visionOS 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 visionOS 27 Beta 7?
This beta release of visionOS 27 brings new features and fixes, particularly enhancing Siri's interaction and improving app storage management. Some changes will only be noticeable once app developers update their apps. The changes Apple documented include activate siri with a glance, localized app storage management, stricter network security.
What are the known issues in visionOS 27 Beta 7?
Apple lists 14 known issues for this build across 10 areas of the system, with workarounds where one exists. They are listed in full on this page under each area.
Should I install visionOS 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 visionOS 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 visionOS 27 Beta 7?
visionOS 27 Beta 7 is build 24M5359a, released on August 24, 2026.
When was visionOS 27 Beta 7 released?
August 24, 2026, 7 days after Beta 6.
Is there a beta profile for visionOS 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 24M5359a you are on visionOS 27 Beta 7. Our build number guide explains how to read them.