Finally, the firewall between the green and blue bubbles seems to be rising—not to block communication, but to secure it! In the iOS 26.5 beta, end-to-end encryption (E2EE) over RCS is now fully enabled. This means that iPhone users on the beta can now exchange encrypted messages with their friends on Android phones (using the latest version of Google Messages), and the appearance of the familiar lock icon confirms that this isn't just marketing hype. Apple, as usual, takes its time testing security features before rolling them out to hundreds of millions of users, so don't worry if you don't see the feature yet.
RCS encryption between iPhone and Android: What actually works in the beta version?
The current situation can be summarized in three key points:
◉ The feature is already working in the testing environment, but it is not available to all users yet, and will not reach the general public until a later update of the 26 series.
◉ The requirements are technically simple but entirely “experimental”.
◉ You will need to install iOS 26.5 beta on your iPhone, and the other party (the Android user) needs the latest version of the Google Messages app.
When these conditions are met and supported by your mobile carrier, a lock icon will appear in the conversation to confirm that encryption is active. It's worth noting that this option is automatically enabled in the settings of supported devices and networks and requires no intervention from you. However, if you don't see the lock icon, you should assume that your messages are currently unprotected, regardless of your operating system version.
The global standard behind the scenes: Why is this change more than just an Apple feature?
Apple didn't build this system in complete isolation, and that's the secret to its expected robustness. The encryption is based on the RCS Universal Profile 3.0 standard, a new technology that Apple helped develop in collaboration with the GSMA. This update moves from version 2.4, which Apple previously shipped, to a version that supports encryption based on the MLS (Message Layer Security) protocol, a globally recognized standard.
The MLS protocol solves the major problem that previously made cross-platform encryption impossible: how to exchange and relay encryption keys between different companies' servers (Apple and Google) without one company controlling the other's keys. This means that iPhones and Android devices can now establish a shared, fully private, encrypted session. And because it's based on global standards rather than a bilateral agreement, it's designed to withstand system updates and future device generations.
What does encryption protect, and what are its true limits?
When this small padlock appears, it provides specific and effective protection; the content will not be readable by carriers or any other party in the message's path. This closes a long-standing security loophole that allowed messages between iPhones and Androids to travel across the internet as completely unreadable text. Now, the "green bubbles" will have the same basic level of protection that the "blue bubbles" have had for years.
However, precision is key. Encryption only protects the content itself; metadata such as who you're talking to, when, and the number of messages remains outside the scope of this encryption. Furthermore, the practices of telecom companies and message backups are separate issues. Therefore, if your security threat is very high, specialized applications like Signal remain the best option, because RCS encryption establishes a "floor" of security for everyone, not an ultimate "ceiling" of absolute privacy.
Timing and what extended tests indicate
Apple's developer notes for iOS 26.4 made it clear that the feature wouldn't be released in that update, and its continued presence in the iOS 26.5 beta confirms that Apple is putting it through multiple software iterations to ensure its stability. The goal is to close a security gap and make cross-platform messaging smarter, as the Universal Profile 3.0 standard also adds features like message editing, deletion, and direct replies in shared conversations.
Ultimately, we are witnessing a fundamental shift in the philosophy of interoperability. Availability will remain dependent on the support of carriers and devices, and the lock icon will remain your sole and secure proof that your conversation is encrypted. This is a significant step towards making communication more secure for everyone, regardless of their preferred bubble color.
Source:
3 comment