iOS 26.5 Encrypted RCS Texts Between iPhone and Android Are Here — But Your Carrier Holds the Key

GigaNectar Team

iPhone Home Screen showing iOS 26 Liquid Glass design with translucent app icons widgets and Dock displayed against a colourful wallpaper

In December 2024, the FBI and CISA jointly warned Americans to stop texting between iPhones and Android phones — because those messages were not encrypted. The backdrop was the Salt Typhoon cyberattack, in which Chinese state-affiliated hackers breached networks at major U.S. telecom carriers including AT&T, Verizon, and T-Mobile. Now, roughly 17 months later, Apple is closing that gap. iOS 26.5, expected in mid-May 2026, will be the first iPhone software update to include end-to-end encryption for RCS messages exchanged with Android users — though carrier support will determine who actually gets it from day one.

This has been a long time coming. Apple added RCS support in iOS 18, but encryption was missing. The GSMA published RCS Universal Profile 3.0 in March 2025, establishing end-to-end encryption via the Messaging Layer Security (MLS) protocol as the new standard. Apple tested the feature in the iOS 26.4 beta but pulled it before that release. It returns — and ships — with iOS 26.5.

iOS 18
When Apple first added RCS support
Mar ’25
GSMA published RCS Universal Profile 3.0 with MLS encryption
Beta
Status of E2EE RCS in iOS 26.5 at launch
Jun 8
WWDC 2026 — iOS 27 reveal date

End-to-end encryption (E2EE) means a message is locked on your device and can only be unlocked on the recipient’s device. Nobody in between — not the carrier, not Apple, not any interceptor — can read it in transit. Before iOS 26.5, an RCS message from an iPhone to an Android phone had no such protection.

Apple’s iOS 26.5 implements E2EE for RCS using the Messaging Layer Security (MLS) protocol, which is the foundation of GSMA’s RCS Universal Profile 3.0. This is the first standardised, interoperable encryption method for cross-platform messaging at this scale. The feature is on by default. You can confirm it at Settings → Messages → RCS Messaging, where you’ll see an “End-to-End Encryption (Beta)” toggle. When active, a lock icon appears in the Messages conversation header.

iMessage conversations between Apple users have been end-to-end encrypted since 2011 (iOS 5). SMS messages, the old green-bubble standard that predates RCS, have never had E2EE and still don’t. That hasn’t changed.

1
Both sides must be ready
Your iPhone must run iOS 26.5 or later. The Android user must have the latest version of Google Messages. If either side doesn’t meet the requirement, the chat stays unencrypted RCS — or falls back to SMS.
2
Your carrier must support it
Unlike iMessage or WhatsApp — where encryption is baked into the app — RCS E2EE is baked into the protocol layer. That means both the sender’s and the receiver’s carriers must support RCS Universal Profile 3.0 for encryption to activate.
3
The lock icon confirms it
When all conditions are met, you’ll see “Text Message · RCS | 🔒 Encrypted” at the top of the conversation on iPhone. On Android, Google Messages shows the same lock icon it already uses for encrypted Android-to-Android chats.
4
It can change mid-conversation
Encryption status is network-dependent. If one user switches to a carrier or network that doesn’t support E2EE RCS, the lock can disappear. This is different from WhatsApp or Signal, which maintain encryption regardless of the carrier.

This is the core limitation. Apple’s release notes state: “End-to-end encrypted RCS messaging (beta) in Messages is available with supported carriers and will roll out over time.” Apple has said it will publish the list of supported carriers on its messaging page once iOS 26.5 ships — the list was not available at the time of the RC release on May 4, 2026.

For the encryption to work, both the sender’s carrier and the receiver’s carrier must support the updated RCS standard. If you’re on a carrier that has upgraded its RCS infrastructure and your Android contact is on one that hasn’t — or vice versa — the conversation will be unencrypted. The lock icon will simply not appear.

This is structurally different from how WhatsApp or Signal work. Those apps control their own encryption at the application layer — it never drops regardless of which network you’re on. RCS E2EE is a carrier-level feature, which makes rollout pace a genuine variable.

E2EE closes the biggest security gap, but it doesn’t make cross-platform RCS equivalent to iMessage. Several features still don’t work when an iPhone texts an Android phone:

Message unsending — iPhone users cannot unsend a message in a cross-platform RCS chat. Message editing — editing is currently only available from the Android side. Emoji reactions — currently limited to the iPhone side in cross-platform chats. Reply threading — replying to a specific message inline doesn’t yet work cross-platform on iPhone.

These missing features are part of the broader GSMA RCS roadmap and are expected in future profile updates. The RCS Universal Profile 3.0 also introduces cross-platform Tapback support and inline replies — but full adoption depends on both Apple and Google updating their clients and carriers updating their infrastructure.

SMS — the oldest text protocol, used when RCS isn’t available — still has no encryption of any kind. That hasn’t changed.

September 2024
Apple adds RCS to iOS 18
iPhones get read receipts, typing indicators, and high-res media sharing with Android — but no encryption on cross-platform messages.
December 2024
FBI/CISA warn Americans after Salt Typhoon
Chinese state-affiliated hackers breach AT&T, Verizon, T-Mobile. U.S. agencies warn citizens to stop unencrypted cross-platform texting.
March 2025
GSMA publishes RCS Universal Profile 3.0
First standardised E2EE spec for cross-platform RCS, based on the MLS protocol. Apple co-authored the specification alongside the GSMA.
March 2026
E2EE tested in iOS 26.4 beta — then pulled
Apple tests the feature but doesn’t include it in the final iOS 26.4 release, citing it as not yet ready.
May 4, 2026
iOS 26.5 Release Candidate ships with E2EE confirmed
Apple’s RC release notes officially confirm E2EE RCS will ship. Feature marked as beta, carrier-dependent rollout.
Mid-May 2026
iOS 26.5 public release (expected)
E2EE RCS goes live for iPhone users on supported carriers. Apple to publish carrier support list on its messaging page at launch.
June 8, 2026
WWDC 2026 — iOS 27 announced
Apple shifts focus to iOS 27, expected in September 2026. iOS 26.5 is the last significant pre-WWDC update.
A
Alex (Android)
Text Message · RCS
🔒 Encrypted
Hey, can you send me those docs?
Sure, sending now.
Delivered · RCS 🔒
Got it, thanks!
End-to-end encrypted. Only you and Alex can read these messages.
🔒
E2EE for RCS (Beta)
● New in 26.5
Cross-platform encrypted messaging between iPhone and Android via MLS protocol. Carrier support required on both ends. Toggle in Settings → Messages → RCS Messaging.
🗺️
Suggested Places in Maps
● New in 26.5
Tapping the Maps search bar now shows recommendations based on nearby trending places and recent searches. Ads in Apple Maps are coming to the U.S. and Canada “this summer.”
🏳️‍🌈
Pride Luminance Wallpaper
● New in 26.5
Dynamically refracts a spectrum of colours with more than 11 variations. Users can select 1 to 12 colours. Paired with a new Pride Edition Sport Loop and watch face for Apple Watch.
💳
New App Store Subscription Type
● New in 26.5
Developers can now offer monthly billing on a 12-month commitment — annual pricing split across 12 payments. Initially available in most countries, excluding the U.S. and Singapore.
Reminders: Exact Snooze Times
● New in 26.5
Snooze options now display specific times (e.g., “3:00 p.m.”) instead of vague phrases like “this afternoon” or “this evening.”
✏️
Cross-Platform Message Editing
◐ Not Yet in 26.5
RCS Universal Profile 3.0 includes edit/delete and inline reply — but full cross-platform support from the iPhone side requires further updates. Currently editable only from Android.
⚠️
The carrier dependency matters. Unlike WhatsApp or Signal — where the app itself controls encryption and it never drops — RCS E2EE is baked into the network protocol. If your carrier or your contact’s carrier hasn’t upgraded to support RCS Universal Profile 3.0, the lock icon won’t appear and the conversation won’t be encrypted, even on iOS 26.5. Apple will publish a list of supported carriers at apple.com/ios/feature-availability when the update ships. For fully carrier-independent encryption right now, apps like WhatsApp and Signal remain the reliable option.

iOS 26.5 was covered here with a focus on its three confirmed additions — end-to-end encrypted RCS messaging (in beta), Suggested Places in Apple Maps, and the Pride Luminance wallpaper — alongside the App Store subscription changes and Reminders snooze updates. The broader Apple hardware and software story continues ahead of WWDC 2026 on June 8, where iOS 27 is set to be announced. The E2EE RCS feature, first tested in iOS 26.4 and confirmed in the iOS 26.5 Release Candidate, was described in Apple’s release notes as available “with supported carriers” and rolling out “over time.” The Salt Typhoon context and carrier dependency noted in this piece were covered as factual background to the update.

For readers interested in related Apple and Google device updates, the iOS 26.5 public release is expected in mid-May 2026. The wider technology landscape surrounding this update was also part of the reporting context.

Leave a comment