Listen to this Post
Introduction
When Apple confirmed it would support end-to-end encryption (E2EE) for RCS messaging, the announcement was framed as a turning point for cross-platform texting. It suggested a future where iPhone and Android users could finally exchange secure, feature-rich messages without falling back to outdated SMS. At the time, iOS 18 was current, and the implication was clear: the next major iOS generation would deliver a fully modern RCS experience. Now, with iOS 26.3 reaching release candidate status, that future still hasn’t arrived. The absence of encryption is only part of the story—several major RCS upgrades remain missing, raising questions about Apple’s rollout strategy and the real timeline for secure RCS on iPhone.
the Original
Apple initially launched RCS support on iPhone using a very limited implementation of the protocol. The company adopted RCS Universal Profile version 2.4, which covered only the basics such as read receipts, typing indicators, and higher-quality media sharing. Crucially, it did not include end-to-end encryption, largely because the open RCS standard itself did not support encryption at that time. That changed with the release of RCS version 3.0, which introduced E2EE as a core feature. Shortly after that release, Apple publicly confirmed it would support encrypted RCS messaging across iOS, iPadOS, macOS, and watchOS in future updates, positioning privacy as a central selling point.
However, as of iOS 26.3 RC, encrypted RCS messaging has still not shipped. Beyond encryption, other important protocol upgrades are also missing. RCS versions between 2.4 and 3.0 introduced major quality-of-life features designed to bring RCS closer to platforms like iMessage. These include proper emoji reactions, custom reactions, in-line replies, and the ability to edit or delete messages. On iPhone today, reactions technically exist but are handled poorly, appearing as fallback text rather than native emoji responses.
The article also highlights recent developments suggesting progress behind the scenes. Some French carrier bundles included with iOS 26.3 beta 2 indicate that certain carriers may soon enable end-to-end encrypted RCS messaging by default. This strongly suggests Apple is preparing the groundwork for a broader rollout, possibly tied to iOS 26.4 rather than the current release. While the wait continues, these carrier-level hints point to RCS upgrades arriving sooner rather than later.
What Undercode Say:
Apple’s cautious approach to RCS tells a larger story about control, timing, and ecosystem politics. From a technical perspective, Apple is clearly capable of rolling out encrypted RCS quickly once the standard is finalized. The delay is unlikely to be about engineering difficulty alone. Instead, it reflects Apple’s long-standing pattern of moving only when the surrounding ecosystem aligns with its privacy narrative and product strategy.
RCS end-to-end encryption is fundamentally different from iMessage encryption because it relies on a cross-industry standard rather than Apple-owned infrastructure. That means Apple must depend on carriers, GSMA specifications, and Android implementations to maintain a consistent security baseline. Any weakness in that chain risks undermining Apple’s privacy messaging, which is one of its strongest brand assets. Shipping a half-baked or carrier-fragmented encrypted RCS experience would be worse, from Apple’s perspective, than delaying it altogether.
The missing RCS 2.7 features are just as telling as the absence of encryption. Message editing, deletion, proper reactions, and in-line replies are not minor conveniences—they define what users now expect from modern messaging platforms. By holding these features back, Apple is effectively ensuring that iMessage remains visibly superior, even while RCS exists as a compatibility layer. This maintains a subtle but important distinction: RCS is “good enough” for Android conversations, but iMessage is still the gold standard inside Apple’s ecosystem.
Carrier bundles hint at a phased rollout strategy. Enabling encrypted RCS first at the carrier level allows Apple to test real-world behavior without flipping a global switch. This mirrors how Apple has handled other sensitive features in the past, such as eSIM transitions and satellite services. If issues emerge, they can be contained geographically rather than becoming a worldwide headline.
There is also a competitive angle. Google has been aggressively promoting RCS as the future of messaging on Android, often positioning Apple as the last major holdout. By waiting until encryption, reactions, and editing are all ready to ship together, Apple can reclaim the narrative and say it delivered a “complete” RCS experience—on its own terms. When Apple finally enables encrypted RCS, it will likely frame the move as an industry-leading privacy upgrade rather than a concession to Android users.
Ultimately, the delay reinforces a familiar pattern: Apple does not rush to match competitors feature-for-feature. It waits until it can integrate those features in a way that strengthens its broader ecosystem strategy. RCS on iPhone is evolving, but it is doing so slowly and deliberately, ensuring that iMessage remains central while cross-platform messaging improves just enough to satisfy regulators, carriers, and users.
Fact Checker Results
Apple did confirm support for RCS end-to-end encryption following the release of RCS 3.0, making the core claim accurate.
iOS currently uses RCS Universal Profile 2.4, which lacks encryption and advanced messaging features.
Carrier bundle references in iOS 26.3 beta builds support the claim that encrypted RCS is being prepared but not yet enabled.
Prediction
Apple will likely introduce encrypted RCS alongside a broader feature upgrade in iOS 26.4, not as a standalone change. When it arrives, Apple will bundle encryption with message editing, deletion, and proper reactions to present it as a major quality leap. This rollout will reduce pressure from regulators and competitors while still preserving iMessage’s premium status within the Apple ecosystem.
🕵️📝✔️Let’s dive deep and fact‑check.
References:
Reported By: 9to5mac.com
Extra Source Hub (Possible Sources for article):
https://www.facebook.com
Wikipedia
OpenAi & Undercode AI
Image Source:
Unsplash
Undercode AI DI v2
Bing
🔐JOIN OUR CYBER WORLD [ CVE News • HackMonitor • UndercodeNews ]
📢 Follow UndercodeNews & Stay Tuned:
𝕏 formerly Twitter 🐦 | @ Threads | 🔗 Linkedin | 🦋BlueSky | 🐘Mastodon
