iOS 26.5 release candidate seeded — adds cross‑platform end‑to‑end encryption

Apple’s Messages app is about to close one of its biggest privacy gaps. On May 4, Apple seeded the iOS 26.5 release candidate, and the release notes confirm that end-to-end encrypted RCS messaging is coming to conversations between iPhone and Android users. The big deal is simple — cross-platform texting has had modern features for a while, but not the same default privacy people expect from iMessage or Signal. Now that’s changing, and the release-candidate stage means public rollout is probably close. (developer.apple.com) ### What changed this week? The new part is not RCS itself. Apple already added RCS support earlier, which brought nicer basics like typing indicators, read receipts, better group chats, and higher-quality media between iPhone and Android. What changed this week is that Apple’s iOS 26.5 RC notes now explicitly say end-to-end encrypted RCS messaging is included(developer.apple.com)ing out over time. (macrumors.com) ### What does “release candidate” mean? A release candidate is basically Apple saying, “we think this is the build.” Developers and testers get one last near-final version before public release, unless a serious bug forces another build. So this is not a vague roadmap promise. It’s a feature sitting in Apple’s near-finished software, tied to a specific version number and release track. (developer.apple.com) ### Why wasn’t RCS already encrypted? Because RCS had a weird split. Google Messages offered encryption in some chats, but that was largely tied to Google’s own implementation, not the shared cross-platform standard everyone uses. The missing piece was an official interoperable spec that Apple, Google, carriers, and other clients could all build against. That (developer.apple.com)5. (gsma.com) ### What exactly did GSMA add? GSMA added end-to-end encryption to the RCS standard using Messaging Layer Security, or MLS. Basically, MLS is the ruleset for how clients create and manage secure group and one-to-one conversations without every vendor inventing its own incompatible system. That matters because encrypted messaging is only truly cross-platform if both sides speak the same security language. (gsma.com) ### Will every iPhone-Android chat be encrypted immediately? Probably not. Apple’s own wording leaves room for a staggered rollout. The feature is marked beta, limited to supported carriers, and Apple says availability will expand over time. So the software support is landing now, but real-world coverage may depend on carrier support, device compatibility, and the Android client on the other side. (theapplepost.com) ### Why does this matter beyond Apple fans? Because default texting still matters more than tech people like to admit. Plenty of families, schools, workplaces, and small businesses live in the preinstalled messaging app. If those cross-platform chats gain real end-to-end encryptio(theapplepost.com) path people already use. (macrumors.com) ### What’s the catch? The catch is that “encrypted RCS” will sound simpler than it is. Users may assume every blue-green conversation is instantly private in the same way iMessage is, but rollout conditions still matter. Carrier support matters. Client support matters. And Apple is still calling this beta, which is a hint that edge cases and uneven availability are part of the launch. (theapplepost.com) ### Bottom line? This is a real shift, not just another beta-note curiosity. GSMA created the standard in March 2025, Apple tested it in iOS 26.4, and now iOS 26.5 RC moves it to the edge of public release. Cross-platform texting is finally getting the privacy layer it should have had years ago. (gsma.com)