Ryan Hens / Android Authority
TL; Dr.
- Apple had earlier confirmed the plan to add end-to-end encryption to RCS messages in future software updates
- Now we have seen the code that suggests that the end-to-end encryption iOS 26 can come in the RCS messages on iPhones.
- The code suggests that Apple would use the MLS protocol launched by GSMA’s Universal Profile 3.0, developed with Apple’s involvement.
After years, Apple finally allowed iPhone users to avail benefits RCS Texting With the release of iOS 18, They are originally given to Android usersWhile RCS brings key features for Android-iOS conversations, such as high quality media, lesson reactions, rich group chats, and more, it lacks a major feature: End-to-end encryption. Apple confirmed that End-to-end encryption is coming on RCS on iPhones “In future software updates.” Now we have found that this can happen soon as iOS 26.
Don’t want to miss best from Android authority,
When the GSMA announced the new Universal Profile 3.0 specifications in March, they mentioned with End-to-end Encryption (E2E) based on the messaging layer security (MLS) protocol. The GSMA said it would make the RCS the first mass messaging service to support the interopeable E2 EE amidst different client implementation.
The new RCS standard was developed in collaboration with mobile operators, device manufacturers and technology providers including Apple. Apple shared the following statements at that time:
End-to-end encryption is a powerful privacy and safety technique that IMESSAGE has supported from the beginning, and now we are pleased to lead a cross industry effort to bring end-to-end encryption into RCS Universal profiles published by GSMA. We will add support for IOS, iPados, Macos, and Watchos end-to-end encrypted RCS messages in future software updates.
The “future software update” is rather unclear, as it can mean any practically any update in the future. Given how much time it took for RCS to reach the iPhone, it is suspected that end-to-end encryption when the iPhone will come in RCS. The good news is that iOS 26 Betus, as far as the first developer Betus, includes codes related to end-to-end encryption:
Apple is testing the same MLS encryption that Google added to Google messages, as you can see in the screenshot below:
This certainly does not mark the iOS 26 as a software version that will bring E2E support to RCS on iPhones, but it at least indicates that the company is working on it in this version. The support end may eventually push into a few later versions, such as iOS 26.1 or later, like iOS 27, but we are optimistic that support may reach later later.
If you were expecting Apple to bake in all features from Universal Profile 3.0, then you should catch your horses. The Apple group does not combine features such as icons and mention (we cannot spot the codes related to them), so there is a good opportunity that the company only clings to facilities like encryption and keeps it bare.
Note that iOS users already enjoy E2ee through IMessage. It only switchs to the stock message app RCS on iPhones when interacting with Android users, which lacks E2EE support. When RCS E2EE support comes on iPhones in future software updates, messages will be encrypted between iPhone and Android users. This means that messages including files and media and their content, will be confidential and safe, and third party, such as messaging provider or cell carriers, will not see the content of these messages.
Android-endroid conversations do not support E2E by default until the two sides use a client app that supports E2EE, such as Google messages. If Android users use various clients, the message will not be E2E. If and when messaging clients adopt new RCs universal profile 3.0 with MLS, they will also support the interopeable E2Ee.
Thanks for being part of our community. Read our Comments policy Before posting.
