On May 4, Apple simultaneously released release candidates for every 26.5 platform: iOS 26.5 RC (build 23F75), iPadOS 26.5 RC (23F75), macOS Tahoe 26.5 RC (25F71), watchOS 26.5 RC (23T570), tvOS 26.5 RC (23L471), and visionOS 26.5 RC (23O471). Xcode 26.5 RC (build 17F42) shipped in the same batch. For devices still running iOS 18, iOS 18.7.9 and iPadOS 18.7.9 (build 22H355) also arrived.
A release candidate is, barring last-minute blockers, the build that ships to everyone. The public release is estimated for the week of May 11: that is based on historical patterns, not an official announcement.
What iOS 26.5 includes
The most widely discussed feature is end-to-end encryption for RCS messages between iPhones and Android devices, built on RCS Universal Profile 3.0 and the MLS (Messaging Layer Security) protocol. The feature ships enabled by default but remains in beta even in the final release, and requires that both sender and receiver use a carrier that supports the updated profile. Availability depends on carrier adoption, not on Apple.
On the App Store side, iOS 26.5 unlocks worldwide availability of monthly subscriptions with a 12-month commitment, excluding the United States and Singapore. Developers who already configured this option in App Store Connect can test it in sandbox against the RC build. The subscription type becomes visible to users at the moment of the public release, on iOS 26.5, iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, and visionOS 26.5.
New Pride Luminance wallpapers are also included. There are no additional consumer features of note beyond what shipped in earlier betas.
iOS 18.7.9 for devices that cannot run iOS 26
iOS 18.7.9 shipped the same day for devices that do not support iOS 26. Security content details had not yet been published at the time of writing. The pattern of recent 18.7.x updates suggests a maintenance patch, but it is worth waiting for the official security page before drawing conclusions about urgency.
What to do now in your development workflow
The RC moment is when the test cycle closes. Three concrete steps:
Update Xcode in CI pipelines. Replace the previous beta or RC with Xcode 26.5 RC (build 17F42). If your pipeline uses xcode-select with explicit paths or preconfigured images, confirm the new build is available. The macos-26 runners on GitHub Actions have been generally available since late February.
Test on a physical device. Install iOS 26.5 RC on at least one device per supported target. Release candidates rarely introduce regressions compared to the last beta, but this is the right moment to confirm compatibility before the software reaches users.
Verify the monthly subscription flow. If you plan to activate the 12-month commitment subscription option at the launch of iOS 26.5, run a full sandbox test now: creation, confirmation of the monthly charge, cancellation, and renewal notification verification.
TestFlight 4.2 shipped on April 30, a few days before the RCs. Apple did not publish detailed release notes with new features.
What remains uncertain
A second RC is possible, though uncommon when the first build shows no known issues. The week-of-May-11 estimate is just that: an estimate, not an official date.
The security details of iOS 18.7.9 are the next item to track, along with any official date announcement for iOS 26.5.
