Developers testing the iOS 27 beta 1 should note that the RCS end‑to‑end encryption toggle is absent. Apple isn’t removing the feature; the first beta is a fork taken from an internal build before the latest 26.x changes are merged. Consequently, shipped features can drop out of early builds and reappear in subsequent ones.

Unlike iMessage, which encrypts every message, standard RCS texts travel in plaintext between iPhone and Android devices. A joint effort by Apple, Google and the GSMA introduced RCS end‑to‑end encryption in iOS 26.5, turning the lock icon on by default when both carriers support it. Users see an “Encrypted” label at the top of qualifying threads.

If encrypted RCS matters, keep your device on the stable iOS 26.5 release until Apple restores the toggle in a later 27 beta. The omission is a safeguard against shipping a half‑functional security control in an unstable build. Expect the feature to return once the 27 branch incorporates the pending 26.x updates.

For cross‑platform messengers, the temporary loss means Android contacts will see green bubbles without the lock indicator, potentially exposing sensitive chats. Enterprises that rely on encrypted RCS for compliance may need to postpone testing on the 27 beta. Once Apple merges the 26.x code, the security parity between iMessage and RCS should be fully restored.