RCS Messages "Not Delivered" since iOS 26.1/26.2 update

I came here to report a similar solution to Bones223.

I realized it was only one person whom this was happening with. I asked them to switch off RCS, reboot their phone, then switch RCS back on. After a full day of messaging, this seems to have fixed the issue. (For now 🤞)

The other user is using Google Messages on a Pixel 9 pro running Android 16.

It's very funny to me that whenever Apple pushes an update that breaks a feature for thousands of users, there is no shortage of fanboys in the forums declaring that the problem is "NOT Apple."

Sure, the problem only started occurring immediately after Apple pushed an update supporting E2EE on RCS, and sure, that update occurred on the notoriously buggy iOS 26.x that needed multiple updates just to fix its flagship Liquid Glass features, and sure, Apple's implentation of RCS has been riddled with issues every step of the way, but there's no way Apple could have possibly caused THIS bug! It's NOT Apple! 🤣

Now if you'll excuse me, I have some buggy 26.x iPhones to fix for their users, because the users couldn't get any help from these useless circle-jerk forums.

For anyone experiencing the issue: this is caused by a bug in iMessage in iOS 26 preventing SMS activity when RCS is detected but considered unavailable for the recipient. The issue was allegedly fixed in 26.3, though it still persists for some users with some contacts.

If you are experiencing it with just one or a few contacts, try asking them to use Google's Messages app to toggle RCS off/on. If they dont use RCS, they'll want to leave it off after toggling it on.

If you're one of the unlucky ones to experience it with all contacts, try disabling/re-enabling RCS in your own settings.

If that doesn't work, just remember that it's definitely NOT Apple, but it'll still probably be resolved in update 26.4.

I had the same problem what ended up fixing it was having the person on android download google messages and enabling RCS messaging (they also have to set google messages as default messaging app in settings) < that part was crucial to getting it to work

RGL1399 wrote:

Just Checking back to see if we have an Answer from APPLE on how to Fix this. i have tried to shut off and reboot the iMessage and the RCS feature. Still having the not delivered issue.

This is a user to user only forum. Apple isn't here. And message issues are most definitely NOT an issue affecting the masses. Messaging is a Carrier provided feature. If you're having an issue with RCS or MMS messaging, your carrier is responsible for that service, NOT Apple. Expecting Apple to answer this issue is not going to happen. Contact your carrier. And elevate it higher with your carrier as most first line people with most carriers have no technical knowledge whatsoever.

After updating to 26.2 and turning "iMessage" OFF!!! It started working for me.

rawritscm wrote:

1. I'm having issues with sending messages/text to an Android user (Samsung Galaxy) via RCS messaging. When I send a RCS text, I receive a "failed to deliver" notification and "not delivered" next to the text. However the receiver does receive the RCS text. I have read receipts on and it goes from "read at XX:XX" to "not delivered" a minute later.

This issue has been ongoing since the iOS 26.1 update on my iPhone 15 Pro. I have since updated to iOS 26.2 and still no resolution. I have tried:

Force restarting - no change

2. Turning iMessage on and off

3. No inactive or duplicate SIM

4. No VPN

5. No issues with phone storage or notifications

These notifications are driving me crazy and I'm always second guessing if my message went through. I'm up for an upgrade soon and seriously considering switching to an Android after all this.

What did your phone carrier say when you reported the issue, and it doesn't matter if you get an Android, as those feature is provided by your phone carrier.

It's common enough. I'm an Android Phone user (Motorola) and I have 4 friends with iPhones that are seeing it when they communicate with me. A few are seeing it when they communicate with some other Android users, but not all. I have plenty of iPhone friends that don't see it when communicating with me. It seems to be an all or nothing thing. Either it doesn't happen at all, or it happens with every message. The only reason I would associate it with Apple is that this entire thread seems to correlate it to the 26.1 release. My carrier is Google Fi. Most of my friends having the issue on their iPhone are Verizon users, but I know of one TMobile user. I also know that one of those iPhone friends is having the same issue when talking to his mom who has a Samsung phone on TMobile. It's not specific to one carrier.

I just posted a similar issue. I turned on all messaging types and now it offers "send as SMS" when not delivered. Doesn't always work and doesn't always show delivered when it does, but it's something. For me, it's usually during a group text that was initiated by an iPhone user in the group.

Destiny_556 wrote:

Do you have any updates? I have been having the exact same issue driving me crazy!

Yes the update is to contact your phone carrier so they can resolve the issue for you.

The weird part for me is that it is only with my husband. Doesn't happen with any other Android user. Nor any other Samsung user. And not even every message to him even. Yes, it started once I updated to 26, but it has to be his phone or carrier not my upgrade since it is just him that it happens with.

rawritscm wrote:

Again, repeating the same comment after stating the carrier had no solution isn’t helpful at all.

Then suggest you find a new carrier or stop paying your bill since it is included in your monthly payment.

I'm having the same problem. Getting failed mail or not delivered notification when the recipient did receive the text. When the recipient reads the msg, I get a read receipt and the failed mail notification disappears. This started after 26.2 install. Just installed 26.2.1 and problem still remains. Apple, please fix this!

Yep I have the same issue and couldn’t figure out how to fix it

Do you have any updates? I have been having the exact same issue driving me crazy!