RCS Encryption Finally Works Between iPhone and Android, But Carriers Are Still the Weak Link

Apple shipped end-to-end encrypted RCS messaging between iPhone and Android in the iOS 26.5 beta in May 2026, closing a gap security researchers had flagged for years: the only common text channel between the two largest mobile platforms sent plaintext over the wire. The cryptography is done. The feature most users will actually get is a different story, because encrypted RCS doesn't work unless both carriers on a conversation support it — and carrier rollout is where this upgrade is quietly stalling.
What Actually Shipped
The new encryption layer implements the GSMA's RCS Universal Profile 3.0 specification, finalized in March 2025, using the IETF's Messaging Layer Security (MLS) protocol — the same class of modern, scalable encryption scheme used in newer group-messaging designs, rather than the older Signal Protocol double-ratchet that WhatsApp and iMessage use. MLS was chosen specifically because it handles large groups more efficiently; RCS group chats can run into the dozens of participants, and double-ratchet encryption gets expensive to rekey at that scale.
On the Apple side, the feature lives in iOS 26.5 for iPhone and requires the latest Google Messages app on Android. Both ends need current software. That part is achievable for most phones in active use — it's the network layer underneath that creates the real bottleneck.
The Carrier Problem Nobody Fixed
RCS, unlike iMessage or WhatsApp, isn't a single company's server routing your message. It's a carrier-mediated protocol — your message passes through your carrier's RCS infrastructure, then the recipient's carrier's infrastructure, before it reaches their phone. Encryption has to be negotiated and supported at every hop. If either carrier in that chain hasn't upgraded its network to support Universal Profile 3.0 and MLS, the message either falls back to unencrypted RCS or, worse, silently downgrades to SMS without clearly telling either user that protection was lost.
That single-point-of-failure design is why the rollout is landing region by region, carrier by carrier, rather than as a single global switch-flip. Apple's own carrier support list already includes a number of major U.S. and Canadian networks, but it is explicitly partial — a list that's being added to, not a completed rollout. A user on an unsupported carrier gets none of the new protection, with no clear interface signal distinguishing "this conversation is encrypted" from "this conversation looks the same but isn't," unless the app surfaces that state explicitly.
Why This Took So Long — and What's Still Missing
Apple and Google agreed in principle to RCS interoperability back in 2024, and cross-platform encryption was always framed as phase two. The technical work — getting two competing platforms to agree on a shared encryption standard rather than each pushing their own — took roughly 18 months from the Universal Profile 3.0 spec to a shipping beta. That's fast by telecom standards and slow by consumer software standards, and it's a preview of how slow everything downstream of this will move, because every future RCS feature now has to clear the same multi-carrier coordination problem.
Universal Profile 3.1, still pending, adds message editing, undo-send, and higher-quality image sharing. Universal Profile 4.0, finalized in February 2026, specifies interoperable cross-platform video calling for groups up to 32 participants — a feature iMessage and FaceTime users have had natively for over a decade, now arriving as a carrier-dependent cross-platform feature roughly 15 years after FaceTime launched. None of that is in the current release; it depends on further carrier upgrades layered on top of the encryption rollout that's still incomplete.
What This Means If You're Texting Across Platforms
If you regularly text between iPhone and Android, there is no reliable way right now to know from the message thread alone whether a given conversation is actually end-to-end encrypted — it depends on both carriers, which is information neither Messages app surfaces clearly to average users. The practical takeaway: don't treat cross-platform RCS as encrypted by default the way you would an iMessage or WhatsApp thread, even on fully updated software, until your specific carrier pairing is confirmed supported. For anything sensitive sent to a contact on a different platform, a dedicated end-to-end encrypted app — Signal, WhatsApp, or iMessage within Apple's own ecosystem — remains the only guarantee that doesn't depend on carrier infrastructure you have no visibility into.