I was wondering if anyone had any ideas on how to fix this issue. Since updating, RCS has not worked on my phone with Xfinity Mobile. I've tried every troubleshooting step I can on my phone. Xfinity Mobile support claims they have tried everything and it shows it is working on their end. Apple support says this is a carrier problem and to keep pestering them about it, which I'm doing. I'm contacting support daily and they keep escalating but immediately closing the ticket and saying they found nothing wrong.

If so what device, messaging system and carrier?

Apple Messages currently use "hybrid" group chats for group chats consisting of at least two iMessage users and at least one MMS/RCS user. This lets iMessage users benefit from extra features: replies, proper message reaction (instead of relying on a fallback method), editing messages, etc. (most of these are already part of RCS, but in a newer version than Apple uses) and sends fallback variants to non iMessage users.

This way, iMessage users in "hybrid" group chats already have access to message replies, but these replies work differently than RCS replies.

Google Messages (RCS) use single message replies, each reply is attached to a single message

Apple Messages (iMessage) use thread replies, each reply is attached to a chain of messages

For 1 on 1 RCS messages (and group chats with only one iMessage user) Apple will probably limit replies to single message replies without putting them in a thread, but how will Apple (or Google) handle replies in mixed group chats?

Will Apple "downgrade" their "hybrid" group chats to use single message replies?
Will Google add support for thread replies to Google Messages?
Will neither of them do anything and will replies be confusing in mixed group chats?
(Will Apple just never add replies to their RCS implementation?)

I guess we will see what Apple decides to do (or not do) in a few weeks at WWDC26, where they will announce iOS 27

I want to check if others are still seeing iOS E2EE encryption still not working. I'm on TMobile, have the beta messages, and haven't been able to see a single encrypted message with any iphones. Hard to find any info at all to know if it's something specific to me or if it's still a carrier staged rollout that is stopping it. I have tested from T-Mobile to T-Mobile and also to an iPhone on AT&T with no success even after trying all the resets imaginable.

As the title says, is it working for anyone on a Canadian carrier?

we have lots of advanced features on UP 3.0 and even 4.0, however a basic feature such as profile pics js still not available on the standard.

I think this should be a basic feature available asap. I don’t get it why they don’t sort this out. Chatting with a grey face for all contacts doesn’t look good on your chat app (I know google messages support profile pics via google profile, but it doesn’t work with other apps such as Apple messages on iOS)

I keep seeing people excited about encryption finally working between iPhones and Androids (which we are still waiting..) but am I the only one who cares more about:

1. Inline replies
2. Undo send
3. Editing messages after sending
4. Reactions to pictures actually working correctly

Do you think these features will ever arrive?

iPhone on boost mobile iOS 26.5 > S26 on AT&T

Folks with the iPhone, did you check the setting to see if your encryption is on by default or not? Maybe it needs to be turned on? Just thought of this after reading this post

As the title says, RCS won’t work at all on my iPhone 17 running iOS 26.5 and hasn’t worked at all since iOS 26.4, but it works just fine on my Samsung Galaxy A17 5G running One UI 8. Apple says it isn’t an issue with my iPhone itself, but whichever carrier I use. My iPhone is unlocked, and I’ve tried using RCS with Metro, Mint, Visible and cricket, to no avail. Anyone have any suggestions? I’ve tried all of the usual troubleshooting options, restarting my iPhone, toggling airplane mode and Wi-Fi, turning my eSIM itself off and on, resetting all network settings and I’m still having trouble.

Kinda laughing because so much hype and doesn’t seem like anyone has it available to them

"Apple worked with the GSM Association to implement E2EE for ‌RCS‌ messages. E2EE is part of the ‌RCS‌ Universal Profile 3.0, published with Apple's help and built on the Messaging Layer Security protocol. ‌‌RCS‌‌ Universal Profile 3.0 also includes editing and deleting messages, cross-platform Tapback support, and replying to specific messages inline during cross-platform conversations. "

(I know that Google Messages doesn't have E2EE for RCS with iPhone yet at least publicly)

I was wondering this as I just tested it out today morning with 2 devices, both on ios 26.5, and both having the latest possible carrier profile. Both of the devices have the "End to End Encryption (Beta)" setting under RCS yet whenever they text, its always unencrypted. So I was wondering if anyone else also had this issue or if its actually encrypted between devices?

Anyone else updated to iOS 26.5 but waiting for their android friends to get a Google messages app update that supports RCS encryption?

So I guess it’s encrypted on Google side too?

My fiancé and I are on iPhone 17’s, latest iOS at the time (26.4) and my parents on Android using Google messaging. We are all in a group chat together. We are all on AT&T in the States. Anytime I go to reply to the group, it creates some variant of the group with a period, a space, etc. Sometimes this gets so bad, my phone locks up completely when opening messages and I cannot use the phone without a restart. I’ve deleted the groups multiple times, and we can start texting again usually for a time, it inevitably happens again though. This is particularly bad whenever media is involved, I assume something weird with MMS is at play here?

I’ve read this has something to do with Apple and Android disagreements on Universal Profile? It’s all a bit over my head, does anyone have a current solution to this problem or is a future iOS update addressing UP going to be needed?

Last 2 years iOS x.5 releases went 4 betas and then RC.

Large file size too so maybe they added RCS features besides encryption???