RCS Messages Not Delivered on iPhone After iOS 26? Here’s the Real Fix

If RCS messages not delivered on iPhone has been happening since you updated to iOS 26, you’re dealing with a real, currently-reported bug — not a settings mistake on your end. It shows up in a specific pattern: RCS keeps working fine on the iPhone itself, but breaks for the same conversation on a connected iPad or Mac. Here’s exactly why that split happens and the actual fix order, not just “toggle it off and on.”

Why This Started With iOS 26

According to Apple’s own RCS documentation, RCS is a carrier-supported service registered through your iPhone’s phone number — unlike iMessage, it isn’t tied to your Apple ID directly. Multiple reports across Apple’s own Community forums describe RCS messages showing “Not Delivered” specifically after updating to iOS 26, and the pattern is consistent: RCS continues working on the iPhone that owns the phone number, but fails when the same conversation is opened from a paired iPad or Mac. That’s because your iPad and Mac don’t connect to your carrier’s RCS network directly — Apple routes RCS through your iPhone as a bridge, the same mechanism used for SMS Text Message Forwarding. When that bridge connection breaks after an update, RCS quietly stops working on every device except the phone itself.

Confirm RCS Messages Not Delivered Is Actually Your Issue

Before troubleshooting, check where the failure is actually happening. Send a test message from your iPhone directly — if it delivers fine from the iPhone but fails from a paired iPad or Mac using the same Apple ID, this is the bridging issue described above, not a carrier outage or a problem with the recipient. If RCS is also failing directly from the iPhone itself, that points to a carrier-side RCS registration problem instead, which the fixes below won’t resolve — contact your carrier in that case.

Fix Order — Try These In Sequence

1. Toggle RCS off and back on. Go to Settings → Apps → Messages → RCS Messaging on your iPhone, turn it off, wait 30 seconds, then turn it back on. This forces a fresh registration handshake with your carrier and resolves a meaningful share of reported cases on its own.
2. Reset Network Settings. Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings clears potentially conflicting APN configurations that can interfere with RCS registration. Note this also resets saved Wi-Fi passwords and VPN configs, so have those handy afterward.
3. Confirm Text Message Forwarding is on for the affected iPad/Mac. Settings → Messages → Text Message Forwarding on the iPhone — if the specific device isn’t toggled on there, it can’t receive the bridged RCS traffic regardless of anything else.
4. Sign out of iMessage and back in on the affected device. On the iPad or Mac, Settings → Messages (or Messages → Settings on Mac) → sign out, restart the device, then sign back in with the same Apple ID.
5. Check for a carrier settings update. Settings → General → About — if a carrier update is available, install it; carriers periodically ship RCS-related fixes through this channel independent of iOS updates.
6. If it’s still broken, contact your carrier directly and ask them to re-provision RCS on your line — some users have resolved this by having their carrier push a fresh registration/reset code, which isn’t something you can trigger from the device alone.

What Happens While It’s Broken

Nothing gets permanently lost. When RCS fails, iOS silently falls back to standard SMS/MMS for that conversation — messages still send, but you lose read receipts, typing indicators, and full-resolution photo/video sharing until RCS reconnects. If you’re specifically seeing the green bubble come back after previously having RCS or iMessage working, that’s this fallback behavior, not a sign anything was deleted or reset.

Match Your Situation

Frequently Asked Questions

Why does RCS work on my iPhone but not my iPad?
Because RCS is registered through your carrier to your iPhone’s phone number specifically, and your iPad relies on the iPhone to bridge that traffic over — the same mechanism SMS forwarding uses. If that bridge breaks, RCS fails on the iPad even though the iPhone itself is fine.

Is this an iOS 26 bug or a carrier problem?
Based on the pattern being reported, it’s most often a bridging issue introduced around the iOS 26.1 update, not specific to one carrier — but if RCS also fails directly on the iPhone itself, that points to a carrier-side registration issue instead.

Do I need iOS 18 or later to use RCS at all?
Yes — Apple’s own documentation confirms RCS messaging requires iOS 18 or later along with a cellular plan from a carrier that supports RCS on iPhone specifically.

Will resetting network settings delete my messages?
No — it clears Wi-Fi passwords, VPN configurations, and cellular settings, not your message history. Your conversations remain intact.

Why did my texts turn back into green bubbles?
When RCS (or iMessage) can’t deliver, iOS automatically falls back to standard SMS/MMS so your message still sends — this shows as a green bubble and is expected fallback behavior, not something broken with your account.

Does every carrier support RCS on iPhone?
No — availability depends on both your carrier and region. If the RCS Messaging toggle is missing entirely from Settings → Apps → Messages, that’s usually a sign your carrier or plan doesn’t support it yet, rather than a bug to troubleshoot.

Can I just turn off RCS and rely on iMessage instead?
Yes, for conversations with other Apple users — iMessage is unaffected by this specific issue since it runs over your Apple ID rather than carrier RCS. RCS only matters for texting Android users with high-res media, read receipts, and typing indicators.

This page may contain affiliate links. If you purchase through one, we may earn a commission at no extra cost to you. See our full Affiliate Disclosure for details.