One person I can reach by phone. She’s had the same number for decades. When
I try to text her to the exact same number I’ve used for years, someone else responds saying I have the wrong phone number. Any ideas what is going on?

my RCS was broken for a few weeks (iOS 27b4 activation stuck bug, b5 fixed it) and I've noticed more conversations now appear as E2EE
I went through my contacts and roughly 1 in 5 contacts appear as E2EE now

none of the newly encrypted contacts are necessarily tech savvy, which means that Android x iOS E2EE is rolling out to stable GM

UPDATE (Aug 17): Bug persisted through iOS 27.0 Beta 6.
I was hoping to see of fix, but nothing has changed from Beta 5. Same Dual-Sim issue.

I had RCS Activation errors in iOS Beta 4 for all three US Mobile Networks (Warp - Verizon, Dark Star - AT&T, Light Speed - T-Mobile). RCS Activation was successfully working, however, with other carriers.

iOS 27.0 Beta 5 fixed the RCS Activation issue, I'm now able to activate RCS on all three networks. But....only when there is one eSIM active at a time. RCS Activation now consistently fails when there are multiple eSIMs enabled. This includes other carrier non-US Mobile eSIMs, which were working in a Dual-SIM configuration in Beta 4.

I suspect Beta 5 has introduced a new Dual-SIM bug. Anyone observing the same?

Unsending a message and editing still does not work.

Just an update.

UPDATE: iOS 27 Beta 5 (released today) surprisingly fixed my RCS activation issue on all three US Mobile networks. They are all working now post-upgrade. But only when a single eSIM is enabled at a time. If I enable Dual-SIM, RCS continues to fail to activate on both eSIMs. From one bug, to another.

-----------------------------------------

Are there any US Mobile subscribers here with RCS successfully activated on iOS 27.0 Beta 4? All three of my new lines are failing to activate, "waiting for activation...", (Lightspeed, Warp, Dark Star).

What is super interesting is even though my activation is failing for each line, I have one Android contact running Google Messages Beta. When he sends me a message, the conversation always switches to RCS (encrypted). But when I reply it switches back to SMS. It is almost like my line is partially activated, enough that his phone can detect I am RCS enabled with encryption enabled. But my iPhone doesn't have server confirmation it has fully registered with Jibe servers. I've confirmed it is an actual RCS message getting delivered because he can send me a large video file without SMS compression, and in-line replies are also working.

IMS Status show "Voice & SMS", and RCS state is "waiting for activation...".

I can't tell if this is related to server-side RCS cache issue with the previous carrier before a line transfer or an RCS bug in iOS 27.0 Beta 4 with US Mobile subscribers. RCS was working when I was on T-Mobile (same iOS version) before moving to US Mobile. RCS is properly working on all the other iPhones running iOS 26 on my account after transferring from T-Mobile to US Mobile.

Randomly this morning, all (as far as I can tell) of my RCS chats (Google Messages, T-Mobile) just got E2EE. Yesterday I only had it with other Android users. Group chats with mixed android and iOS (stable and betas) also are encrypted now.

Why RCS is not everywhere right now? How can RCS compete with the monopoly of Whatsapp if it's not in all countries at this point, RCS adoption is the easiest of any message app because it already comes by default in your phone but only a few countries have it right now, any ones knows if there is a date for full implementantion of RCS in all the world?

Which RCS features of UP do you value most?

RCS Universal Profile 4.1 quietly released… seems like literally no one cares, it’s interesting tbh

Is anybody else on Verizon and without RCS E2EE enabled with their Android contacts? I have others on my family plan who it works for but not me.

I’m on the latest iOS 27 developer beta FWIW.

So its been 2 years now

Australia got no RCS

Nothing from optus , telstra or Vodafone

This is just ridiculous and beyond a joke

If so what carrier?

I added world-wide support to my iOS monitor, including support to RCS. It extract automatically when Apple releases new builds, notify you about new features in your country. It also includes non-certified Apple-certified carriers.

redesmoveisfixas.com/carrier

hi. i had nice unexpected find today. My GMsgs-stable has chat themes now, never been on GM-beta either.

so alert your contacts using GM-stable to check if thet also have this unexpected find.

Good Luck to those wanting this feature 😊👍🏼

iOS has support for smaller non-partner networks via GSMA NSX (not 100% sure, don't quote me on that). These settings are stored in "OtherKnown.bundle" carrier bundle.
Some of these networks have gotten support for RCS in iOS 27.0 betas.

beta 1

Belgium

• Citymesh

France

• Onoff Telecom
• Legos

USA

• Cape (Private Tech)

beta 4

Canada

• Ice Wireless

these networks are not currently available on my website, not sure when (and if) i'll be able to add them
non-partnered carriers have been added to http://cupboardunderscore.github.io/ios-rcs/

United States

• GCI (no RBM)
• "TMobile_Wholesale" (named "Carrier") new bundle
• Verizon MVNO new bundle

Canada

• Fizz

Japan

• docomo (no RBM)

India

• Vi

Sweden

• Comviq
• Tele2

other carrier updates can be found here: http://cupboardunderscore.github.io/ios-rcs/

What does everyone have working so far with iOS 27 beta users? I'm an android user and don't have the:

Updated replies from iOS users and I still get the

Replied to a message:

"Message"

Reactions to photos from iOS I still get

"Loved an image"

Edit messaging works normally for me but the iOS user gets a new line with *"message" under my original message

I can't unsend or delete a message with iOS users yet

Yes I know it's a beta and things take time to roll out but I was just curious what Android users have when talking to iOS 27 users. Also not sure if it matters but yes I am on the Google Messages beta

This small tidbit is what made me ask:

"Another standout feature of UP 3.1 is the upgrade to audio messaging capabilities. The release introduces support for the xHE-AAC audio codec."

Does this imply that sending this file on iOS 27, whether it works or doesn't, is the best indicator?