Created
March 9, 2026 22:20
-
-
Save applch/561246a2c3c69b9ae293107c4ccb9a76 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| iOS & iPadOS 26.4 Beta 4 Release Notes | |
| Update your apps to use new features, and test your apps against API changes. | |
| Overview | |
| The iOS & iPadOS 26.4 SDK provides support to develop apps for iPhone and iPad running iOS & iPadOS 26.4 beta 4. The SDK comes bundled with Xcode 26.4, available from the Mac App Store. For information on the compatibility requirements for Xcode 26.4, see Xcode 26.4 Release Notes. | |
| Address Sanitizer | |
| Known Issues | |
| Address Sanitizer and Thread Sanitizer might hang on macOS 26.4, iOS 26.4, tvOS 26.4, watchOS 26.4, and visionOS 26.4 when building with Xcode 26.3 or older. (171762808) | |
| Workaround: Use Xcode 26.4 when testing applications with Address Sanitizer or Thread Sanitizer. | |
| Background Assets | |
| New Features | |
| You can now check the status of an asset pack while offline by calling localStatus(ofAssetPackWithID:) or assetPackIsAvailableLocally(withID:) on the shared asset pack manager. The former method returns all available status information. The latter returns only a Boolean value but can be called synchronously. Not all status information is available offline. (164498466) | |
| You can make the latest version of an asset pack available locally by calling ensureLocalAvailability(of:requireLatestVersion:) on the shared asset pack manager and passing true to the shouldUpdate parameter. (166237389) | |
| Resolved Issues | |
| Fixed: Apps might crash when downloading asset packs. (169648111) | |
| External Media | |
| Resolved Issues | |
| Fixed: HFS external media might fail to mount automatically. (168672160) | |
| Feedback | |
| Resolved Issues | |
| Fixed: After submitting a crash/panic report, Feedback UI’s close button might become unresponsive. (170091186) | |
| Memory Integrity Enforcement for Applications | |
| New Features | |
| Applications can now opt in to the full protections of Memory Integrity Enforcement for enhanced memory safety protection. Previously applications were limited to Soft Mode. (160719439) | |
| Messages | |
| New Features | |
| In this beta, RCS end-to-end encryption will become available for testing between Apple and Android devices. This feature is not shipping in this release and will be available to customers in future iOS, iPadOS, macOS, and watchOS 26 releases. End-to-end encryption is in beta and is not available for all devices or carriers. Conversations labeled as encrypted are encrypted end-to-end, so messages can’t be read while they’re sent between devices. (170160585) | |
| Networking | |
| Resolved Issues | |
| Fixed: Multiple processes leak CFRunLoopSource objects when Automatic proxy configuration (PAC) or Auto proxy discovery are configured. | |
| For clients of the CFNetworkExecuteProxyAutoConfigurationURL and CFNetworkExecuteProxyAutoConfigurationScript API, please check to make sure your process is not working around the leak by overreleasing the CFRunLoopSourceRef returned by those functions or the CFArrayRef and CFErrorRef passed to the completion. (166839810) (FB21376045) | |
| Reality Composer | |
| Known Issues | |
| Reality Composer iOS can no longer export projects as .reality or USDZ. Opening export menu results in an empty panel. (170091896) | |
| StoreKit | |
| New Features | |
| New fields revocationType and revocationPercentage have been added to Transaction. (148858551) | |
| Resolved Issues | |
| Fixed: Purchase Intents might not be emitted from the intents sequence when the app is launched from the background. (168958783) (FB21767675) | |
| SwiftUI | |
| Resolved Issues | |
| Fixed: SwiftUI does not surface the latest .userActivity as the current user activity. (163136831) | |
| Known Issues | |
| Multiple implicit SwiftUI animations (triggered by RealityViewContent.animate or Entity.animate) that modify a RealityKit component’s properties, are combined only when the implicit animations target the same set of component properties. | |
| For example, if you initiate an implicit animation on Transform.scale and then initiate an implicit animation on Transform.scale and Transform.translation then the animations affecting the scale property will be independent of each other, and will not combine. In this case, the most recently initiated animation will overwrite the scale property. (169723142) | |
| Workaround: Ensure the same component properties are animated by subsequent implicit animations when possible. | |
| UIKit | |
| Resolved Issues | |
| Fixed: KeyboardNotification might not send. (165479264) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment