What's New in iOS 27 Beta 7
This iOS and iPadOS 27 Beta 7 release is primarily for developers, with changes that will affect users once app developers adopt them. It includes new features for audio accessories, health tracking, and game controllers, as well as improvements to dictation accuracy.
-
Improved dictation accuracy
Dictation can now be more accurate with a new on-device model. You can enable this feature in the Keyboard settings under Dictation by toggling on 'Advanced Dictation Preview'.
Dictation can now be powered by a new on-device model that boosts accuracy. To enable this, go to Keyboard settings > Dictation and Toggle on “Advanced Dictation Preview”.
Apple's own words, from the Dictation section of the notes
-
New health tracking features
HealthKit now supports tracking heart rate and cycling power zones, as well as menopausal state and bleeding after menopause. These features require app updates to be available to users.
HealthKit now supports heart rate and cycling power zones.
Apple's own words, from the HealthKit section of the notes
-
Support for new game controller
The PlayStation® Access™ controller is now compatible with iOS, iPadOS, and macOS. Users can create custom input profiles and save them to their Apple devices.
The PlayStation® Access™ controller is now supported on macOS, iPadOS, and iOS. You can create custom input profiles in game controller settings and save them to your Apple device.
Apple's own words, from the Game Controller section of the notes
-
Audio accessory enhancements
Third-party audio accessory manufacturers can now provide headphone information to support fixed spatial audio. This feature is currently for developer testing and will be available to EU customers in a future release.
AudioAccessoryKit now allows third-party audio accessory manufacturers to provide headphone information to the system to support fixed spatial audio. It is only available for developer testing on iPhone and iPad in this release, and will be available to customers in the EU in a future iOS 27 and iPadOS 27 release.
Apple's own words, from the AudioAccessoryKit section of the notes
-
Localized asset packs for apps
Apps can now reduce storage usage by using localized asset packs, which are delivered based on the user's preferred languages. This requires app updates to take effect.
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
Summarised by us from iOS & iPadOS 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 91 areas of the system — 64 new features, 195 resolved issues, 24 known issues, 11 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.
AirPlay1 Resolved Issues
Resolved Issues
- Fixed: AirPlay to Home Theaters fails when a PIN or password is required.
AirPods Max 21 Resolved Issues
Resolved Issues
- Fixed: You cannot update AirPods Max 2 firmware beta in iOS 27 Beta 1 and macOS 27 Beta 1. AirPods Max 2 firmware beta updates are supported in iOS 27 Beta 2 and macOS 27 Beta 2.
AirPort Utility1 Deprecations
Deprecations
- AirPort Utility will no longer be available for new downloads from the App Store. If you previously downloaded the app, you can still re-download it. When using AirPort Utility on iOS 27 and later, functionality is not guaranteed.
App Intents1 New Features6 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: Non-SF Symbol custom images for app entities might not always appear in Siri.
- Fixed: Default values from schemas might not be applied for parameters that are of “Set” type.
- Fixed: Entities you register using RelevantEntities for the workout audio context might not appear as suggestions in Fitness media picker.
- 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.
Apple Wallet1 Resolved Issues
Resolved Issues
- Fixed: Updating to iOS 27.0 Beta 3 or 4 might cause Digital ID to expire and become unavailable for presentation affecting any device signed in to the same Apple Account, not just the device being updated.
AudioAccessoryKit1 New Features
New Features
- AudioAccessoryKit now allows third-party audio accessory manufacturers to provide headphone information to the system to support fixed spatial audio. It is only available for developer testing on iPhone and iPad in this release, and will be available to customers in the EU in a future iOS 27 and iPadOS 27 release.
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.
Battery / Power Management1 Resolved Issues
Resolved Issues
- Fixed: Devices with a deeply discharged battery might fail to boot into the OS and remain stuck on the red dead battery icon screen indefinitely until the device is rebooted or the power adapter is unplugged and reconnected.
Camera1 Resolved Issues
Resolved Issues
- Fixed: In the Camera app, Portrait mode blur effect might render incorrectly for photos.
CarPlay6 Resolved Issues1 Known Issues
Resolved Issues
- Fixed: CPNavigationSession ETA Tray panel items might not receive focus.
- Fixed: The panel delegate method panelDidHide(_ panel: CPMapPanel) might not be called.
- Fixed: Under certain configurations, CPMapPanel might not dismiss when you tap the close button.
- Fixed: The symbol button handler of CPMapPanelButtonConfiguration might not be called.
- Fixed: Your vehicle’s next and previous track steering wheel buttons might not function correctly in CarPlay.
- Fixed: In CarPlay, playback of stereo music content might be silent after playback of Spatial Audio content.
Known Issues
- Siri might respond more slowly than expected in CarPlay, particularly under higher device temperatures or poor network conditions. Workaround: Try the request again after the device has cooled down or once you are in an area with better cellular reception.
Clock1 Resolved Issues
Resolved Issues
- Fixed: You might be unable to stop a ringing alarm from the lock screen without unlocking your device.
CloudKit1 Resolved Issues
Resolved Issues
- Fixed: Saving a CKShare in which an administrator participant has changed their own role to CKShareParticipantRole.privateUser (self-demotion) has no effect.
Communication Safety1 Resolved Issues
Resolved Issues
- Fixed: Sensitive QRCode detected as non-sensitive, preventing 3rd party developers from testing API functionality.
Control Center1 Resolved Issues1 Known Issues
Resolved Issues
- Fixed: The “Add a Control” button in edit mode might appear small and clipped.
Known Issues
- Gathering PowerProfiler and Lookback traces through the Performance Trace Control Center widget might fail to produce traces. Workaround: Gather traces on iOS 27.0 beta 1 or earlier.
Core AI2 New Features11 Resolved Issues
New Features
- iOS 27 includes Neural Engine improvements for Apple Intelligence capable devices. The system now restricts background access to the Neural Engine, similar to GPU usage restrictions. Large model loading (over 1 GB) performance is improved on the Neural Engine. Neural Engine memory usage is now attributed to your app process instead of the system, and appears in the Allocations instrument.
- Access to the Neural engine when your app is in the background requires the new entitlement: “com.apple.developer.background-tasks.continued-processing.inference”.
Resolved Issues
- Fixed: AIModelCache entries might not honor the cache policy you provide, causing re-specialization to occur more often than expected.
- Fixed: When inference runs on the GPU, InferenceFunction.encode blocks until all compute is complete instead of returning as soon as encoding is done, unless the model is specialized with a preferred compute device of GPU.
- Fixed: Certain weight and activation configurations may not run on the Neural Engine, such as FP8-quantized weights and activations, palettized weights with quantized (non-Float16) values, and sparse weights. Affected models may run on the CPU or GPU instead.
- Fixed: When you run InferenceFunction.run on functions with both state arguments and outputs with dynamic shapes, the framework might be unable to infer the shape of the outputs and throw an error.
- Fixed: On-device specialization fails when loading an .aimodel converted with coreai-torch v0.4.0.
- Fixed: Inference might fail or crash for models with control flow over dynamic-shape tensors (for example, linear-attention LLMs such as Qwen3.5/3.6).
- Fixed: Ahead-of-time (AOT) compilation might fail unexpectedly for certain models.
- Fixed: When Metal API Validation is enabled, CoreAI models might fail to execute.
- Fixed: Models with custom Metal kernels will fail to load.
- Fixed: App-group support might not work as expected on certain model types.
- Fixed: On-device specialization might fail when loading an .aimodelc compiled ahead of time using Xcode 27 Beta 2 or earlier.
Core Bluetooth1 Resolved Issues
Resolved Issues
- Fixed: The Channel Sounding API in Core Bluetooth is not returning ranging results.
Core Spotlight1 Known Issues
Known Issues
- Creating a SpotlightSearchTool without a configuration and using it with a LanguageModelSession backed by the on-device system language model fails with an error reporting that the number of tokens provided exceeds the maximum allowed. The tool’s default configuration is sized for models with large context windows, so the tool’s description and parameter schema alone exceed the on-device model’s context window before any prompt is added. Workaround: Configure the tool with a focused guide, which uses a compact schema sized for the on-device model: To search a specific kind of content, pass a domain: .focused(.communications), .focused(.calendar), .focused(.documents), .focused(.visualMedia), or .focused(.audio). A focused guide exposes a smaller set of search capabilities than the default configuration. Sessions backed by a model with a larger context window can continue to use the default configuration.
Developer Settings1 Resolved Issues
Resolved Issues
- Fixed: Deep links into Settings > Developer > Paired Macs might silently fail to navigate to the target Mac computer. The Paired Macs pane loads correctly when entered manually.
Dictation1 New Features4 Resolved Issues1 Known Issues
New Features
- Dictation can now be powered by a new on-device model that boosts accuracy. To enable this, go to Keyboard settings > Dictation and Toggle on “Advanced Dictation Preview”.
Resolved Issues
- Fixed: The “New Line” and “All Caps” formatting commands might not work reliably in the dictation UI.
- Fixed: When you explicitly dictate punctuation— such as “Period” or “Colon” — both the spoken command word and the punctuation character might be inserted instead of the punctuation character alone.
- Fixed: Dictation might not recognize names from your contacts.
- Fixed: Dictation might insert extra words at the end of a dictated passage that you did not speak.
Known Issues
- Voice Editing commands such as “Change X to Y”, “Delete X”, and “Undo/Redo” might not work reliably.
Family Settings1 Resolved Issues
Resolved Issues
- Fixed: Family member’s Ask To Buy, Apple Cash, Purchases, Subscription rows cannot be accessed.
Files2 Resolved Issues
Resolved Issues
- Fixed: Deleting files from Recently Deleted might fail with an error or experience significant delays.
- Fixed: Users might be unable to delete or open a file whose name contains certain Unicode characters if the name was created before this issue was addressed.
Finder1 Resolved Issues
Resolved Issues
- Fixed: Suggested names for a file or folder might be more generic than its contents. For example, a folder containing only bird photos might receive suggestions like “Wildlife” or “Animal Photos” rather than bird-specific names.
FindMy1 Resolved Issues
Resolved Issues
- Fixed: Siri might not be able to find some of the people sharing location with you in FindMy.
First-Party App Search1 Resolved Issues
Resolved Issues
- Fixed: Search assets might download slowly for languages and regions other than English and the United States, causing degraded search experiences for first-party apps up to a few hours after you install or upgrade to the latest OS, change your device language, or region.
Fitness+1 Resolved Issues
Resolved Issues
- Fixed: On larger iPhones in landscape orientation, the Workout Detail view may display duplicate title text and action buttons when browsing workouts or meditations.
Foundation1 New Features1 Resolved Issues
New Features
- volumeAvailableCapacityKey is truncated to 3 significant decimal digits at the block count level (e.g., 123,456,789 blocks becomes 123,000,000 blocks).
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.
Game Center1 Resolved Issues
Resolved Issues
- Fixed: When you trigger the Access Point, its completion handler is never invoked.
Game Controller1 New Features
New Features
- The PlayStation® Access™ controller is now supported on macOS, iPadOS, and iOS. You can create custom input profiles in game controller settings and save them to your Apple device.
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.
HealthKit3 New Features1 Resolved Issues
New Features
- HealthKit now supports heart rate and cycling power zones.
- Updated HealthKit permissions flow now lets users grant apps access to limited history or full history.
- HealthKit adds support for tracking menopausal state and bleeding after menopause; two new sample types are available. HKCategoryTypeIdentifierMenopausalState records a person’s current menopausal state. Values defined by HKCategoryValueMenopausalState are menopause, perimenopause, and none. HKCategoryTypeIdentifierBleedingAfterMenopause records bleeding episodes occurring after menopause. Values use the existing vaginal bleeding flow levels: unspecified, light, medium, and heavy. Both types are read/write, classified under Reproductive Health, and require the standard HealthKit category type authorization.
Resolved Issues
- Fixed: null unit might incorrectly convert to count and percent units.
Hearing Test1 Resolved Issues
Resolved Issues
- Fixed: During a Hearing Test, visual feedback might not appear when you tap the screen to indicate a tone was heard.
Home Screen2 Resolved Issues
Resolved Issues
- Fixed: Switching between many different posters with different icon tints may cause system sluggishness.
- Fixed: The Home Screen Customization on a newly setup device might not save.
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.
Image Playground4 Resolved Issues
Resolved Issues
- Fixed: When VoiceOver is enabled and the gallery contains only one image, the prompt input UI might not appear.
- Fixed: When Image Wand encounters an error — such as an unsupported flow or unsafe output — you might see the misleading message “Connect to Wi-Fi to create images” even when your device is already connected to Wi-Fi.
- Fixed: If required models are downloading, you might see an error message instead of download progress information.
- 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.
iPhone Mirroring3 Resolved Issues
Resolved Issues
- Fixed: In rare cases, iPhone Mirroring may not resize correctly even after pressing the home button in the mirroring app.
- Fixed: Restarting an app while iPhone Mirroring is active can result in the screen appearing to freeze and resizing being disabled.
- Fixed: iPhone Mini does not resize properly during iPhone Mirroring.
Keyboard1 Resolved Issues
Resolved Issues
- Fixed: Unlocalized text can appear for paste candidates.
LDCM1 Resolved Issues
Resolved Issues
- Fixed: When your device’s charging port is wet but empty, you might see a dialog instructing you to unplug a charger or accessory even though nothing is connected.
Lock Screen3 Resolved Issues1 Known Issues
Resolved Issues
- Fixed: After dismissing Lock Screen, the Lock Screen grabber might appear in the incorrect location or orientation.
- Fixed: Siri and Search may still be available when locked even if they are disabled under “Allow Access When Locked” in Settings.
- Fixed: Portions of Depth Effect–enabled wallpapers might appear earlier than expected while pulling down Notification Center.
Known Issues
- Starting a Vision Pro Guest Mode session might result in two Live Activities on screen at the same time. Workaround: Dismiss the Lock Screen and re-lock the device.
Mail1 Resolved Issues
Resolved Issues
- Fixed: Emails might display content that doesn’t match their subject line.
Mail Banners1 Resolved Issues
Resolved Issues
- Fixed: Mail banners for early flights will show the flight status as delayed.
Media Sharing Extensions1 New Features1 Resolved Issues
New Features
- New frameworks allow you to add media sharing protocols through extension at the system level and enable media apps to use these extensions through a common API framework.
Resolved Issues
- Fixed: Due to a mismatch in runtime checks with the mandatory entitlement for MediaSharingExtensions, extensions using the new MediaDeviceExtension framework can build but don’t run on target devices.
Messages3 Resolved Issues
Resolved Issues
- Fixed: Stickers attached to a message from an unknown sender do not appear.
- Fixed: GIFs and pasted images might render as the incorrect size.
- Fixed: HDR screenshots might appear garbled when sent in Messages.
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.
MetricKit7 New Features2 Deprecations
New Features
- CrashDiagnostic now includes a terminationCategory that maps to the corresponding case in ForegroundTerminationMetric and BackgroundTerminationMetric.
- Apps that emit developer-defined states through the StateReporting framework now receive metrics and diagnostics in the context of those states.
- MemoryExceptionDiagnostic are available when your app or app extension is terminated for exceeding its memory limit.
- A new application-level MetalFrameRateMetric is available for Metal frame pacing rendering insights per CAMetalLayer.
- A new Swift-first MetricManager API enables your app to receive MetricReport and DiagnosticReport objects through AsyncStream. MetricReport contains a daily aggregated entry along with interval-based breakdowns that are typically a few hours each.
- LocationActivityTimeMetric now includes a reducedAccuracy property that reports the time your app spent tracking location using reduced accuracy (kCLLocationAccuracyReduced). Xcode’s simulated metric payloads also include sample data for this accuracy level, so you can test against it before your app receives real reports.
- HitchTimeMetric.ratio and SignpostIntervalMetric.hitchTimeRatio now use the new HitchTimeRatio type, a Dimension subclass that expresses hitch time as a ratio of milliseconds hitching per second of tracked duration. Recompile your app with the latest SDK to pick up this type change and avoid any crashes on launch.
Deprecations
- The original MetricKit APIs — including MXMetricManager, MXMetricManagerSubscriber, MXMetricPayload, and MXDiagnosticPayload — are no longer recommended for new adoption. Use MetricManager instead.
- The scrollHitchTime(_:) case of MetricResult and the ScrollHitchTimeMetric type are no longer part of the new Swift MetricKit API, and MetricReport values no longer contain scroll hitch entries. Use the hitchTime(_:) case and HitchTimeMetric instead, which report per-app animation hitch time. Recompile your app with the latest SDK to avoid a missing symbol crash if it references ScrollHitchTimeMetric or scrollHitchTime(_:).
Nearby Interaction1 Resolved Issues
Resolved Issues
- Fixed: The Channel Sounding API in Nearby Interaction does not return ranging results.
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 .
NetworkExtension1 Resolved Issues
Resolved Issues
- Fixed: When an active VPN configuration sets includeAllNetworks to true, excludeLocalNetworks fails to exclude wired connections to CarPlay.
Notifications1 Resolved Issues
Resolved Issues
- Fixed: Critical alerts are automatically turned on for any apps that request your permission to enable notifications.
NowPlaying1 Resolved Issues
Resolved Issues
- Fixed: Newly created RemoteMediaSession won’t be visible in control center if created while the app is open in the foreground.
On Demand Resources1 Deprecations
Deprecations
- On Demand Resources and the NSBundleResourceRequest API are deprecated. Use Background Assets instead.
PencilKit1 Deprecations
Deprecations
- __PKStrokeRenderState has been renamed to PKStrokeRenderStateReference, with PKStrokeRenderStateReference.init(…) replacing PKStrokeRenderState.asObjCRenderState().
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.
Photos4 Resolved Issues
Resolved Issues
- Fixed: When opened from a grid of Photos search results in Siri on iPadOS, the single-photo viewer might appear blank.
- Fixed: You might see a slight shift in color hues after applying Spatial Reframing to photos.
- Fixed: When sharing a Live Photo from the Photos app, you might not be able to disable the Live Photo effect prior to sending.
- Fixed: Photos app might quit unexpectedly when you re-enter the Extend tool on a photo that has already been extended.
Photos Edit1 Resolved Issues
Resolved Issues
- Fixed: A thin white line might be visible in photos that have had Spatial Reframing applied.
Podcasts1 Resolved Issues
Resolved Issues
- Fixed: On first launch after updating, you might experience longer-than-expected library migration times, which might last several minutes.
RealityKit1 New Features3 Resolved Issues
New Features
- The Gaussian Splat Component API in RealityKit will be available in an upcoming release.
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.
Related Receipts1 Known Issues
Known Issues
- The disclaimer “Siri found in Mail or Photos. Not shared with card issuer” does not appear below displayed transaction related receipts in Wallet for Apple Pay, Apple Card, and Apple Cash.
Reminders1 Known Issues
Known Issues
- After you tap “Add to Reminders” in Messages, the “New Reminder” interface presents the reminder with an empty title field. Workaround: Tap “Add to Reminders” in the “New Reminder” interface to create the reminder, then edit the title in the Reminders app.
Safari3 Resolved Issues
Resolved Issues
- Fixed: The Safari tab bar might enter a state where it does not appear on screen.
- Fixed: Safari Intelligence features might appear as available before assets are fully downloaded. If you use the feature before assets are available, it won’t function correctly.
- Fixed: On iPad, the tip prompting users to automatically organize their tabs might not appear in Safari.
Safari Extensions1 Resolved Issues
Resolved Issues
- Fixed: Turning on or off Safari extensions created via the “Describe an Extension” feature might not take effect until Safari is relaunched.
Screen Time1 Resolved Issues
Resolved Issues
- Fixed: Screen Time restrictions might not apply to child accounts despite being configured.
Security1 Resolved Issues
Resolved Issues
- Fixed: Obtaining new certificates via ACME fails. New MDM enrollments using Managed Device Attestation fail.
SensorKit1 Resolved Issues
Resolved Issues
- Fixed: PPG sensor reader might return no samples when attempting to fetch data.
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.
Shortcuts4 Resolved Issues2 Known Issues
Resolved Issues
- Fixed: Focus automations migrated from iOS 26 to iOS 27 do not work.
- Fixed: Writing Tools actions are unavailable in Shortcuts.
- Fixed: The Use Model action might fail to run when using the On-Device option for some output types.
- Fixed: Shortcuts containing the Send Message action might fail to import or share.
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).
Siri37 Resolved Issues9 Known Issues
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: When location data is unavailable or only coarse-accuracy location data is available, Maps searches initiated through Siri might return empty or imprecise results.
- Fixed: When you turn off Siri, some photo-related questions might return web search results instead of prompting you to share the photo with ChatGPT.
- Fixed: When you ask Siri to work with reminder lists, you might need to use the exact list name. Siri might not recognize similar or partial list names.
- Fixed: App Intents with @UnionValue types that accept a PlaceDescriptorEntity and a String always receive String values instead of PlaceDescriptorEntity entities.
- Fixed: Starting a call with Siri might fail with an error in apps that adopt CallKit and the phone.startCall AppSchema.
- 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: You might not see names and images of email senders in the Siri email list UI.
- Fixed: Siri might not resolve some entity types when your app has provided only an EntityStringQuery for the entity type.
- Fixed: Siri functionality during software updates is limited, including calls to emergency services.
- Fixed: Asking Siri to call short phone numbers, such as “Call 17”, might fail.
- Fixed: Search results from third-party apps may not be tappable.
- 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: Siri cannot create a recurring reminder or update an existing reminder to be reoccurring.
- Fixed: With AirPods connected to iPhone and Announce Notifications enabled, responding “yes” by voice or head gesture to a long incoming notification (for example, a message) prompts you to unlock iPhone instead of reading the full message aloud.
- Fixed: New American English Siri voices 6 and 7 might default to legacy US voices when your device is overheated or in Low Power Mode.
- 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 ask Siri to find, search, or read reminders, Siri might list or read the reminders instead of showing a snippet. When reminder lists are displayed, the list color might not appear correctly.
- Fixed: Mail older than 6 months might not be searchable by body content, but is still searchable by sender and subject.
- Fixed: After enabling Expressive Voices, you are not able to modify Pace or Expressiveness in the Settings pane.
- Fixed: Siri might run the incorrect OpenIntent or system.open intent when multiple intents targeting different entity types are available in your app.
- Fixed: After creating a list through Siri, tapping the list icon might result in an error instead of opening the list in the Reminders app.
- Fixed: When you tap the Send button in the Siri message confirmation flow, the message might fail to send.
- Fixed: When you ask Siri to open a URL from the Siri App, Safari might launch to a blank screen.
- Fixed: On CarPlay with Apple Intelligence and the ChatGPT extension enabled, asking ChatGPT a question through Siri might not produce a spoken answer. The Siri orb appears briefly and the microphone reopens without Siri responding.
- Fixed: You might encounter build failures when attempting to implement a Transferable IntentValueRepresentation for PHAsset.
- Fixed: When asking Siri to call, message, or email a contact, Siri might fail to resolve the correct person — particularly when multiple contacts share the same name, when group names contain emoji or special characters, or when relationship labels (e.g., “my brother”) are ambiguous. In some cases, Siri might pick the wrong contact, fail to present a disambiguation prompt, or freeze during the disambiguation UI.
- Fixed: For Report a Concern flows started with Siri, the text in attachments might be difficult to read while in Dark Mode.
- Fixed: Businesses with overnight hours might display as “Closed till [next day]” even during open hours.
- Fixed: In CarPlay, when Apple Intelligence enabled, Siri requests for directions in Maps might fail to start navigation.
- Fixed: Siri might not respond to your voice correctly.
- Fixed: In the Siri app, conversations might be deleted a few minutes after receiving streaming responses.
- Fixed: When you say “Save Parking Location,” the parking location information displays with reduced detail compared to Beta 1.
- Fixed: On macOS, Siri AI cannot search within specific folders such as Desktop or Documents. File searches might return results from unintended locations.
- Fixed: When the Camera app is open, the Siri “orb” waveform will not animate correctly on some older iPads and “Hey Siri” requests might fail. Affected devices are iPad Air (5th generation, 2022), iPad mini (7th generation, 2024), iPad Pro 11-inch (3rd generation, 2021), and iPad Pro 12.9-inch (5th generation, 2021).
- Fixed: Siri encounters an error when asked to compose emails if the Mail app is not open in the background.
Known Issues
- After Siri returns photo search results and you select photos, Siri might not detect which photos are selected on screen. Commands like “Send these” might apply to all photos returned from the search rather than only the selected ones. Workaround: Open Photos, select the photos you want to act on, then perform the action using Siri — for example, “Send these photos to Bob”.
- Siri doesn’t support voice commands to interact with specific photos. For example, you can’t refer to photos by number, such as “photo one” or “photo four.” Workaround: Use the photo picker to select the photo you want, or tap to select photos directly.
- 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.
- When you ask Siri to add photos to an album, the confirmation prompt and spoken response might report or display more photos than will actually be added. Workaround: Add photos to the album manually in the Photos app: tap Select, tap the photos you want to add, tap the Share button, tap Add to Album, then tap the album.
- Non-SF Symbol custom images for entities might not appear in Siri results for third-party apps.
- When you ask Siri to read your last message, Siri might read an unread message from an unknown sender, such as spam, instead of the most recent message from a known contact. Workaround: Name the sender in your request – for example, “Read my last message from .”
- Siri might respond more slowly than expected in CarPlay, particularly under higher device temperatures or poor network conditions. Workaround: Try the request again after the device has cooled down or once you are in an area with better cellular reception.
- Siri might cut off the end of words during navigation. Workaround: Reduce voice expressivity from the fastest pace, or turn off expressive voices.
- 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.
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.
StandBy1 Resolved Issues
Resolved Issues
- Fixed: StandBy Clocks may be missing.
Status Bar1 Known Issues
Known Issues
- Status bar might appear blurred while apps are in the foreground. Workaround: Restart your iPhone.
StoreKit4 New Features4 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: 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.
Suggestions in Messages1 Resolved Issues
Resolved Issues
- Fixed: The app icon shown for navigation suggestions is always the Apple Maps icon. If the suggestion is selected, the user’s preferred navigation app is correctly launched.
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.
SwiftUI23 New Features13 Resolved Issues1 Known Issues1 Deprecations
New Features
- You can now use .toolbarColorScheme(colorScheme, for: .statusBar) to set a preferred status bar color scheme.
- 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.
- In apps built with the iOS 27.0 and iPadOS 27.0 SDKs, a Text view with .textSelection(.enabled) applied now supports user-interactive selection using the system text selection UI. Previously, selectable Text views on iOS and iPadOS offered selection functionality through a callout menu. When building with the iOS 27.0 and iPadOS 27.0 SDKs, selectable Text views might include additional gestures for system text selection interactions. Consider using .highPriorityGesture() for custom gestures applied to Text views that should supersede system text selection gestures.
- 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 iOS 27.0 and macOS 27.0 SDKs, selectable Text views now support TextRenderer.
- 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.
- In apps built with the iOS 27.0 and iPadOS 27.0 SDKs, a TabView enforces that its selection is set to a visible tab. TabView might crash when its selection is set to a hidden or otherwise unavailable tab.
- You can use .toolbarVisibility(hideStatusBar ? .hidden : .automatic, for: .statusBar) to conditionally hide the status bar.
- The menu bar on iPadOS 27.0 and macOS 27.0, as well as context menus on macOS 27.0, present a reduced set of menu item images. By default, SwiftUI now hides all menu item symbol images in most contexts, while non-symbol images remain visible. Review the updated Human Interface Guidelines to determine which menu items in your app should still display images. Use the labelStyle(_:) view modifier with the .titleAndIcon style to indicate that a menu item Label’s icon should always be shown — such as when the menu item represents an object or a concept rather than an action. SwiftUI continues to automatically provide default visible menu item images for certain common system-wide menu items, such as Settings, Share, and Print.
- 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 iOS 27.0 SDK, you can display non-interactive content on external display scenes using the .sceneAccessory view modifier with an ExternalNonInteractiveAccessory type.
- 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.
- You can use toolbarMinimizationBehavior to control bar minimization behavior. This modifier replaces toolbarMinimizeBehavior.
- 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: In apps built with the 2027 SDKs, tapping the status bar to scroll a ScrollView to its top correctly updates a bound scrollPosition. Previously, the binding could be left holding a stale value because the scroll-to-top transition didn’t drive the scroll-phase updates that propagate to the binding.
- Fixed: A custom TextRenderer applied via .textRenderer(_:) now takes effect on a Text view that also has .textSelection(.enabled) applied. Previously, the custom renderer was dropped on selectable text, falling back to default rendering.
- 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: Retroactive conformances of SwiftUI types to Equatable are not consulted when SwiftUI compares their values.
- 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: 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: When you present a fullScreenCover with a .navigationTransition(_:) and set @FocusState to true via .onAppear, the keyboard does not animate concurrently with the zoom transition. Instead, it waits for the entire zoom animation to complete before the keyboard begins animating up, resulting in a visually jarring 2-step animation.
- 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.
Known Issues
- Progress reported in DocumentReader.read(from:progress:) and DocumentWriter.write(snapshot:to:previous:progress:) might not be presented.
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.
System Experience2 Resolved Issues
Resolved Issues
- Fixed: When Siri is off and your iPad is extended to an external display where Spotlight is on screen, disconnecting the display might cause the system to crash.
- Fixed: After using iPhone Mirroring or other non-main display experiences, a black pill may appear on the CarPlay screen.
System Stability1 Resolved Issues
Resolved Issues
- Fixed: Devices might freeze or panic when idle.
TextKit1 New Features
New Features
- NSTextTable and its related objects and types are available to UIKit clients starting with OS 27 releases.
Trust Insights1 New Features
New Features
- You can now use the TrustInsights framework in your apps by declaring the TrustInsights capability on your app target in Xcode. The framework requires an entitlement and internet connectivity to return results.
UIKit9 New Features13 Resolved Issues2 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.
- iOS and iPadOS apps built with the 27.0 SDK or later are required to include a launch screen. Your app’s Info.plist must contain one of the following keys: UILaunchStoryboardName, UILaunchStoryboards, UILaunchScreen, or UILaunchScreens. Apps that don’t include a launch screen are rejected when the App Store begins accepting apps built with the 27.0 SDK.
- On iOS 27.0 and iPadOS 27.0, Siri can load resources from drag interactions installed in your app’s interface. For example, when Apple Intelligence is invoked from a context menu, the system calls UIDragInteractionDelegate methods to load the content. Because drag sessions might begin without a user-initiated drag gesture, avoid performing animations or presenting modal UI for the drag in dragInteraction(_:sessionWillBegin:). Instead, perform those actions in dragInteraction(_:sessionDidMove:).
- In apps built with the iOS 27.0 SDK, a presented view controller inherits its trait collection by walking up its view’s superview chain through the intermediate views of the presentation, rather than jumping directly to the presentation controller. Custom UIPresentationController subclasses or view controllers that depend on receiving traits directly from the presentation controller might need to update how they propagate or override traitCollection.
- On iPadOS 27.0 and macOS 27.0, the menu bar and context menus present a reduced set of menu item images and do not display images set on menu elements by default. You can use the new preferredImageVisibility property on UIMenuElement — including updated initializers on UIMenu, UIAction, UICommand, and UIKeyCommand — to customize the visibility of each element’s image in these menus. Review the updated Human Interface Guidelines to determine which menu elements in your app should display images. UIKit automatically provides default visible menu element images for certain common system-wide menu items, such as Settings, Share, and Print.
- In apps built with the iOS 27.0 SDK, when UISearchController uses center search-bar placement, the scope bar appears inline on the same row as the search field rather than on a separate row beneath it. When the search field is hosted inside a navigation bar, the scope bar sits inline beside the search field within that navigation bar.
- In apps built with the iOS 27.0 SDK, windowExternalDisplayNonInteractive scenes are no longer offered automatically by the system. Use UIViewController.registerSceneAccessory(_:) with a UISceneAccessory.externalNonInteractive instance to display non-interactive content on external display scenes.
- Use UINavigationItem.navigationBarMinimization to control navigation bar minimization behavior. This property replaces UINavigationItem.barMinimizeBehavior and UINavigationItem.barMinimizationSafeAreaAdjustment.
- The container view of a UIScrollEdgeElementContainerInteraction may contribute its size and position to the overall shape of the scroll edge effect.
Resolved Issues
- Fixed: In apps built with the iOS 27.0 SDK, the deprecated status bar accessors on UIApplication — including statusBarFrame, statusBarOrientation, statusBarStyle, and isStatusBarHidden — might return NaN or null values.
- Fixed: On iPad, if your iPad app is built with the iOS 27 SDK and its UISupportedInterfaceOrientations doesn’t include all four interface orientations, the app is treated as non-continuously resizable. Beginning with iOS 27, supported interface orientations should no longer be a condition for continuous resizability.
- Fixed: The UISceneClosureConfirmation API does not present a confirmation dialog.
- Fixed: The UIMenuLeaf protocol is missing the subtitle property introduced in iOS 16.0.
- Fixed: The background might not appear on a bottom toolbar when you use UIBarButtonItem.hidesSharedBackground to hide a toolbar item’s glass background.
- Fixed: In iPhone Mirroring, if your app is built with the iOS 27 SDK its scene will support all interface orientations regardless of the orientations declared in UISupportedInterfaceOrientations or returned by UIViewController.supportedInterfaceOrientations. Supported interface orientations should be honored until the user begins resizing the window.
- Fixed: In iPhone Mirroring, if your app is built with the iOS 27 SDK and sets UIRequiresFullScreen, its scene receives continuous resize updates when the user resizes the window. Each resize should instead be delivered as a discrete change to a new UIScreen with an updated bounds.
- Fixed: In iPhone Mirroring if your app is built with the iOS 27 SDK, its scene is initially connected to a UIScreen that isn’t UIScreen.main. The scene should start on the main screen.
- Fixed: On iPad, if your iPad app is built with the iOS 27 SDK and sets UIRequiresFullScreen, the bounds of UIScreen.main changes when the user resizes the window. The bounds of the main screen should remain fixed once the screen connects.
- Fixed: On iPad, if your iPad app is built with the iOS 27 SDK and sets UIRequiresFullScreen, its scene receives continuous resize updates when the user resizes the window. Each resize should instead be delivered as a discrete change to a new UIScreen with an updated bounds.
- Fixed: On iPad, if your iPhone-only app is built with the iOS 27 SDK its scene continues to honor supported interface orientations after the user resizes the window. After the first resize, the scene should ignore supported interface orientations.
- Fixed: On iPad, if your iPhone-only app is built with the iOS 27 SDK and sets UIRequiresFullScreen, its scene receives continuous resize updates when the user resizes the window. Each resize should instead be delivered as a discrete change to a new UIScreen with an updated bounds.
- Fixed: On iPad, if your iPhone-only app is built with the iOS 27 SDK and supports only portrait or only landscape interface orientations, its layout breaks when the iPad is in an orientation the app doesn’t support.
Deprecations
- Apps built with the latest SDK must adopt the scene-based life cycle or they fail to launch. For migration guidance, see .
- canOpenURL: is deprecated. Attempt to open the URL and handle any failure instead of validating it first. Using universal links instead of custom URL schemes removes the need for this validation entirely.
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.
Voice Control1 Resolved Issues
Resolved Issues
- Fixed: Voice Control might not respond when using Flexible Item Names to describe items on the screen.
Watch Connectivity1 Resolved Issues
Resolved Issues
- Fixed: The WCSession.transferCurrentComplicationUserInfo method does not work with complications built using WidgetKit on watchOS.
Weather Highlights1 Deprecations
Deprecations
- Weather Highlights is currently only available in US English.
WidgetKit1 Resolved Issues
Resolved Issues
- Fixed: Your widget extension might not render its timeline when it uses an App Intent with a @UnionValue parameter, and content such as images might not appear. This affects WidgetConfigurationIntent types that you declare with a @UnionValue property.
Writing Tools1 Known Issues
Known Issues
- Writing Tools becomes unresponsive when you interact with the Plus button while Writing Tools is in use. Workaround: Force quit Messages to resolve the issue.
Xcode1 Resolved Issues
Resolved Issues
- Fixed: The Simulator might display a black wallpaper and blank app icons temporarily during first boot.
Source: iOS & iPadOS 27 Beta 7 Release Notes, Apple Developer Documentation. Captured when this build was current — Apple replaces that page with each new beta.
What iOS 27 Beta 7 Is
iOS 27 Beta 7 is build 24A5424a, released on August 24, 2026. It is a pre-release build available through the developer and public beta channels, and it supersedes every earlier iOS 27 beta.
It arrived 7 days after Beta 6 (24A5418b, 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 iOS 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 iOS 27 channel. The build appears in Software Update like any ordinary update.
If you are already on an earlier iOS 27 beta, this arrives as a normal update and no re-enrolment is needed. Our full iOS 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 iOS 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 24A5430a, 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 iOS 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 iOS 27 Beta 7?
This iOS and iPadOS 27 Beta 7 release is primarily for developers, with changes that will affect users once app developers adopt them. It includes new features for audio accessories, health tracking, and game controllers, as well as improvements to dictation accuracy. The changes Apple documented include improved dictation accuracy, new health tracking features, support for new game controller.
What are the known issues in iOS 27 Beta 7?
Apple lists 24 known issues for this build across 14 areas of the system, with workarounds where one exists. They are listed in full on this page under each area.
Should I install iOS 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 iOS 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 iOS 27 Beta 7?
iOS 27 Beta 7 is build 24A5424a, released on August 24, 2026.
When was iOS 27 Beta 7 released?
August 24, 2026, 7 days after Beta 6.
Is there a beta profile for iOS 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 24A5424a you are on iOS 27 Beta 7. Our build number guide explains how to read them.