Apple seeds iOS 26.5 RC2

Apple just pushed a second release candidate for iOS 26.5 and iPadOS 26.5. That sounds minor — and mostly it is — but it usually means the software was almost done, then Apple found something worth fixing before shipping. The bigger story is the update itself. iOS 26.5 looks like the release that finally brings end-to-end encrypted RCS messaging into Apple’s world, which matters because iPhone-to-Android texting has been the awkward middle ground for years. ### What actually shipped on May 8? Apple’s developer releases page shows iOS 26.5 RC 2 and iPadOS 26.5 RC 2, both build 23F77, posted on May 8, 2026. The first 26.5 release candidates for Apple’s platforms had arrived on May 4, so this second RC showed up just four days later — basically a quick cleanup pass before the public build. (developer.apple.com) ### Why does “RC 2” matter? A release candidate is supposed to be the version Apple could ship as-is. When there’s an RC 2, the usual read is simple — Apple found a bug, compatibility issue, or regression late in testing. Apple hasn’t publicly spelled out what changed in this second candidate, and even coverage from the Apple rumor press says the differences aren’t yet clear. (developer.apple.com) ### What’s the big feature in iOS 26.5? The headline feature is encrypted RCS. Apple’s developer documentation for iOS 26.5 adds new TelephonyMessagingKit hooks for checking whether an RCS service and the remote device support end-to-end encryption, plus message properties and secure send receipts for encrypted RCS traffic. That is the tell — this isn’t just richer texting, it’s Apple wiring secure cross-platform messaging into the stack. (developer.apple.com) ### Why is that a bigger deal than it sounds? Because Apple’s current support pages still describe ordinary RCS as not end-to-end encrypted. RCS already improved the ugly parts of SMS — better media, read receipts, typing indicators, Wi‑Fi delivery — but the privacy gap remained. iMessage had encryption. Standard iPhone-to-Android RCS generally did not. iOS 26.5 looks like the release that starts closing that gap. (developer.apple.com) ### Does this mean every iPhone-Android text is suddenly private? Not automatically. Apple’s own developer docs make this sound capability-based. The software can check whether the RCS service supports end-to-end encryption and whether the other end supports it too. So the catch is carrier support, service support, and device compatibility still matter. If those pieces aren’t there, the encrypted path may not be available. (support.apple.com) ### Is there anything else in 26.5? The public-facing 26.5 release notes haven’t been fully mirrored on Apple’s consumer update page yet, but the developer notes show a pretty light release outside this messaging change. Most of the visible notes are developer and bug-fix items — StoreKit fixes, subscription metadata fixes, and a wallpaper bug fix. That makes the RCS encryption piece stand out even more. (developer.apple.com) ### So when does the public update land? Apple hasn’t posted a public release date in the sources here. But a second RC this close to the first one usually means launch is near unless another blocker appears. The pattern is familiar — Apple gets one more build into testers’ hands, watches for breakage, then flips the public switch. That’s inference, but it’s a pretty grounded one. (developer.apple.com) ### Bottom line This isn’t a flashy iPhone release. It’s a plumbing release — but useful plumbing. If Apple really ships encrypted RCS broadly in iOS 26.5, the green-bubble experience gets a lot less compromised, and that’s been overdue for a long time. (developer.apple.com)