Skip to Content

Apple Begins Testing End-to-End Encryption for RCS Messages in iOS 26.4 Beta

Apple is testing secure messaging between Android and iOS devices with iOS 26.4, iPadOS 26.4, and macOS Tahoe 26.4. The updates introduce end-to-end encryption (E2EE) for RCS messages, a security feature that is not currently available for cross-platform messaging.

RCS Feature 1
Apple has been working with the GSM Association to implement E2EE for ‌RCS‌ messages. iMessage, the messaging protocol for sending texts between iPhones, has long supported end-to-end encryption. ‌RCS‌ messages between Android devices have also featured E2EE, but there was no full encryption for Android to iPhone (or vice versa) communications. With the addition of E2EE for ‌RCS‌, messages between ‌iPhone‌ users and Android users will eventually be just as secure as iMessage.

Developers running the iOS 26.4 beta will see a new switch in the Settings app that's turned on by default. The toggle enables testing end-to-end encrypted ‌RCS‌ messaging for supported devices and carriers. Most carriers that support ‌RCS‌ will also support ‌RCS‌ end-to-end encryption, according to Apple. During the first beta, ‌RCS‌ encryption is available for testing Apple devices only when iMessage is disabled.

‌iPhone‌ users who have the beta installed will see a lock icon in ‌RCS‌ chats, with the icon indicating that E2EE is enabled. The lock icon will also now appear in iMessage chats.

‌RCS‌ End-to-end encryption for Apple devices will roll out to beta users gradually, so not everyone will have access right away. Encryption will become available over time, and you can tell if it's enabled through the lock icon.

Cross-platform testing between ‌iPhone‌ users and Android users will begin at a later date.

E2EE for ‌RCS‌ will require Apple to update to ‌RCS‌ Universal Profile 3.0, which the GSMA published with Apple's input. Apple currently supports ‌RCS‌ Universal Profile 2.4. ‌RCS‌ Universal Profile 3.0 will also add features for editing text messages, deleting text messages, and replying to specific messages inline during cross-platform conversations.

Apple released the first betas of iOS 26.4, iPadOS 26.4, and ‌macOS Tahoe‌ 26.4 today, with the updates available for developers. Apple plans to launch the updates in the spring, but while E2EE is in testing, the full functionality is not expected until a later iOS 26 update.

Related Roundups: iOS 26, iPadOS 26
Related Forum: iOS 26

Popular Stories

Apple Announces Special Event in New York Feature 1

Apple Teases 'A Big Week Ahead' With Announcements Starting Monday

Thursday February 26, 2026 6:06 am PST by
Apple CEO Tim Cook today teased "a big week ahead," with announcements starting Monday. His post included an #AppleLaunch hashtag with a colorful Apple logo, along with a short video that ultimately shows an Apple logo on the lid of a Mac. Apple is reportedly planning a three-day stretch of product announcements from Monday, March 2 through Wednesday, March 4, with up to five new products...
iphone fold text

iPhone Fold Crease Measurements Revealed as Device Hits Production

Wednesday February 25, 2026 5:37 am PST by
Apple has submitted production line orders for its upcoming foldable iPhone, effectively confirming that the device will launch this year, claims a Chinese leaker. According to the Weibo account "Fixed Focus Digital," assembly lines recently received the orders from Apple, which has apparently allowed the leaker to learn the crease measurements for the device's 7.8-inch inner display....
m3 macbook pro blue

M5 Pro and M5 Max MacBook Pro: What to Expect

Wednesday February 25, 2026 3:02 pm PST by
Apple is working on a new MacBook Pro that could launch next week ahead of the "Special Experience" planned for March 4, so we thought we'd highlight all of the rumors about the device so far. Design There are no rumors of design changes, and we are expecting the upcoming M5 MacBook Pro models to look just like the M4 versions. Apple will continue to offer 14-inch and 16-inch size options,...

Top Rated Comments

2 weeks ago

There have been recent reports of some carriers dropping support for RCS. Perhaps, because they don’t want to pay to implement something that they’re not going to get paid for. Even for those that haven’t dropped support, how many will want to add something that the majority of users (outside the US) won’t have a need for?
Most RCS servers are run by Google. Even large carriers use their services. As long as Google supports RCS encryption, there is little incentive for Carriers to not support it.
Score: 4 Votes (Like | Disagree)
HouseLannister Avatar
2 weeks ago

I didn't realize this feature isn't fully out yet. It's definitely not a priority for Apple; Apple is only privacy focused when convenient.
Apple announced this in March 2025. It is a travesty that they have dragged their heels this long.
Score: 3 Votes (Like | Disagree)
2 weeks ago

Apple should just release iMessage for Android. I read in the past they didn’t want to because it might drive users away from iPhone but times have changed a bit since then. I hate having to use WhatsApp but difficult to quit as so many people use it (especially for group chats).
It‘s too late for that. They had all the momentum over a decade ago but refused to coordinate and take over with WhatsApp being on the rise after iMessage. It‘s imho one of the biggest generational fumbles Apple had being this stubborn.

The article claims Apple still rolls out all the nice user facing features like reactions and editing messages, I have the feeling Apple will just call it a day and not stay truly UP compliant.
Score: 3 Votes (Like | Disagree)
2 weeks ago
Fantastic to see this. However not sure how long carriers will take to support it. Hopefully it won't take long and it will be available everywhere soon.
Score: 2 Votes (Like | Disagree)
2 weeks ago

That‘s not entirely true. GSMA spec has e2ee evaluated by region, not individual carriers. Like if your region / country has E2EE enabled, all carriers have it enabled. At least that‘s how it‘s written in spec, no idea if that‘s how they execute it.
I'm aware the specifications allows client side not carrier or hub, local law compliance when it comes to E2EE. Google enabled e2ee by default and like i said, it is not carrier dependent.

Requirement R5-43-1: RCS clients must enable E2EE by default unless local regulations expressly prohibit it.

Requirement R5-43-1-1: The RCS client provider is required to enable or disable E2EE for all their users in a "market of operation".

Requirement R5-43-1-2: The RCS client provider shall not enable or disable E2EE for a subset of users, or for individual users in a market of operation.

Requirement R5-43-1-3: If E2EE is disabled, the user must be informed that the feature is not available in their market of operation.


it requires an update on the Android side too, no?
No, Android already supports this. The wait is on iOS to catch up which is what Apple is testing now.

And the carrier RCS servers?
Yes, but RCS as it is has almost by default converged to Google Jibe network.
Score: 2 Votes (Like | Disagree)
HouseLannister Avatar
2 weeks ago

I’m confused. The authors said it was put in for 26.3. And other sectors and companies like carriers and androids had to implement.

Or was it just precursor code? And this is now testing?
They saw a bit of code for a couple French carriers, which made everyone think it was coming soon. But not part of 26.3.

It's also just a test at this point. Might not be part of 26.4 GM either.
Score: 2 Votes (Like | Disagree)

🔗 Related Apple News & Rumors

Stay updated with the latest Apple ecosystem news and verified rumors