Toggle sidebar Toggle sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

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

MacRumors

MacRumors

macrumors bot
Original poster


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.jpg

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.

Article Link: Apple Begins Testing End-to-End Encryption for RCS Messages in iOS 26.4 Beta
 
Article Link
https://www.macrumors.com/2026/02/16/ios-26-4-rcs-encryption-testing/
Last edited:
  • Wow
  • Love
Reactions: Z-4195 and SFjohn
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?
 
MacRumors said:
Carriers will need to add support for encryption
Click to expand...
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?

SMS only became a thing (such that, even for systems that didn’t support GSM, they spent the money to create a feature that worked like it) because people were willing to change carriers in order to have it. It was always about their ability to make money (or keeping subscribers which = money). Are there massive numbers of people willing to change carriers to have encrypted RCS? Maybe in the US?
 
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).
 
  • Like
  • Disagree
Reactions: Exxhara and Premium1
dlondon said:
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).
Click to expand...
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.
 
  • Like
Reactions: bluecoast, michaelnugent and dkh587
Zenman12 said:
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?
Click to expand...
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.
 
  • Like
Reactions: michaelnugent and Zenman12
Unregistered 4U said:
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?
Click to expand...
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.
 
  • Like
Reactions: bluecoast, MrSnirf, michaelnugent and 1 other person
TimFL1 said:
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.
Click to expand...
With how people are using these services and the amount of regulation Apple’s being placed under for controlling Apple products, they dodged a serious bullet. That “fumble” meant that iMessage was not widely used enough in the EU to be regulated, so they can run it as they see fit.
 
  • Like
Reactions: Halmahc and Exxhara
MrSnirf said:
Its not dependent on carriers. Its dependent on Google Jibe which as we know support E2EE.
Click to expand...
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.

RCS spec is a mess anyways, Apple doesn‘t give 3 doodoos about it as evident by their subpar implementation of the standard.
 
dlondon said:
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).
Click to expand...
I agree. Apple is using Gemini… so they should drop their pride and let Google pay them to allow/install/incorporate iMessage into phones running Android
 
  • Disagree
  • Haha
Reactions: Exxhara and iPAU
TimFL1 said:
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.
Click to expand...
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.

WarmWinterHat said:
it requires an update on the Android side too, no?
Click to expand...
No, Android already supports this. The wait is on iOS to catch up which is what Apple is testing now.
WarmWinterHat said:
And the carrier RCS servers?
Click to expand...
Yes, but RCS as it is has almost by default converged to Google Jibe network.
 
  • Like
Reactions: bluecoast and WarmWinterHat
This wouldn't be necessary if Apple made iMessage available for Android. Keeping it exclusive to iPhone was one of the dumbest decisions Apple ever made. 😡 Steve Jobs had the right idea. Get people interested in Apple by giving them a taste of Apple. iTunes for Windows. Safari for Windows (while it lasted). iCloud for Windows. In his words, it's like handing a glass of water to someone in hell.
 
  • Like
  • Love
  • Disagree
Reactions: mburkhard, Exxhara, dkh587 and 1 other person
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.
 
Will be curious if they actually support in-line replies and edits in RCS, I have little faith in Apple to do the right thing.
 
  • Like
Reactions: dkh587
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back