Tuesday, May 12, 2026
ap7i.com
🛡️
Adaptive Perspectives, 7-day Insights
Technology

Encrypted RCS Isn't as Easy as Expected

iOS 26.5 ships encrypted RCS, but actually seeing the lock icon in a conversation requires three things to line up — and only one of them is on the iPhone side. Most Android contacts won't get there without being asked.

By R.A.Parks 5 min read
Encrypted RCS Isn't as Easy as Expected

Yesterday’s post here described what Apple shipped in iOS 26.5: a beta of end-to-end encrypted RCS, with all three major US carriers on board at launch. That’s accurate. What it doesn’t convey is what it takes to actually see the lock icon in a conversation today.

Three things have to line up. The iPhone side is the easy one. The other two are on the Android side, and at least one of them won’t happen unless someone asks.

Gate 1: iOS 26.5 on the iPhone

I have an iPhone 16 Pro on AT&T. This is the trivial part. Update to 26.5. Confirm Settings → Messages → RCS Messaging → End-to-End Encryption (Beta) is on, which is the default. Apple shipped its Universal Profile 3.0 client to every supported iPhone at once, so as soon as the update lands, your side is ready.

Gate 2: Google Messages beta on the Android side

This is the gate most people won’t pass through on their own.

Encrypted RCS uses GSMA’s Universal Profile 3.0 spec with IETF Messaging Layer Security underneath. Apple shipped the iPhone client on May 11. Google is shipping the Android client through Google Messages, but the UP 3.0 build is currently in the beta channel — not the stable Play Store release. Your Android contact has to enroll their account.

Here’s the walkthrough, because the Play Store hides this:

  • Open the Play Store.
  • Search for Google Messages.
  • Tap the app listing itself — not the “Open” button. Google Messages is preinstalled on Pixels and most stock Android devices, so the search result shows “Open,” which launches the app instead of taking you to its Play Store page. You have to tap the row to get into the full listing.
  • Scroll past What’s new, About this app, Data safety, and the ratings block. The Join the beta card sits near the bottom and is easy to miss.
  • Tap Join. You’ll see “Joining beta… Adding your account to the program. It may take a few minutes.”
  • Wait a few minutes, then check the Play Store for app updates yourself — it doesn’t push a notification. A new version of Google Messages will be in the list. The update being available is itself confirmation that the enrollment worked. Install it.

This is not something most of your friends or colleagues are going to do unless asked. People don’t join beta channels of messaging apps for fun. If you want an encrypted thread with a specific Android contact, the practical step is to text them the walkthrough and wait for them to come back saying it’s done.

Some Pixel users may already be on a UP 3.0–capable build because Pixel Feature Drops ship ahead of stable Android. Joining the beta improves the odds; it doesn’t guarantee anything, because Google’s final UP 3.0 ramp is server-side on their end.

Gate 3: Carrier support, with a wrinkle

In addition to my iPhone on AT&T, I also have a Pixel 9 on Google Fi. AT&T is on Apple’s supported list. T-Mobile — the network Fi runs on — is on the supported list. Multiple T-Mobile MVNOs are too: Metro by T-Mobile, Mint Mobile, Ultra Mobile. After updating the iPhone, joining the Google Messages beta on the Pixel, and installing the beta build, I expected the lock icon on texts between the two phones.

It didn’t appear.

Apple’s list matches on carrier identity, not on the underlying network. Google Fi isn’t on it. Several T-Mobile MVNOs are, but Fi isn’t one of them, and there is no toggle on either device that overrides that. The iPhone will not initiate an encrypted session with a recipient whose carrier identity isn’t whitelisted, regardless of which tower they’re actually on.

This is consistent with Fi’s pattern from the previous RCS rollout — it was months late getting basic iOS-to-Android RCS interop in 2024–2025, even while running on T-Mobile’s network the whole time. The likely path forward is the same: Fi will land on Apple’s list eventually, on its own timeline.

Bottom line

If you have a friend on Android who is willing to join the Google Messages beta, and they’re on a carrier on Apple’s whitelist, you can probably get an encrypted thread going today. The lock icon should appear when all three gates open.

What’s missing from the launch coverage is that none of this happens by default. The iOS 26.5 update was a step in the direction of encrypted cross-platform RCS — Apple’s own language calls it a beta, not a finished feature — and the Android side is staged the same way. Whether and when the lock icon shows up in a specific conversation depends on what your contact has installed, which carrier their phone is registered to, and how far Google’s server-side ramp has reached.

That’s a more honest version of the news than “Apple shipped encrypted RCS today.”

Sources