RCS Messages Not Sending? A 2026 Cross-Platform Fix

RCS messages not sending is almost always a registration or status problem, not a broken app. Your chat bubble might say “Connecting,” fall back to SMS, or stall on one contact. Check whether RCS is verified for your number first, then work down to Carrier Services and the app cache.

#Why Are RCS Messages Not Sending?

RCS sends fail for four main reasons. The fix depends on which one you’re hitting, so read what the chat shows when a message stalls.

A message stuck on “Sending” with a spinning circle points to a live connection or registration issue. A message that quietly converts to a green or gray SMS bubble means RCS gave up and fell back. A red exclamation mark usually means the recipient or the network rejected the delivery.

Here’s the quick triage we use before touching any settings.

What you see	Likely cause	Where to look first
Stuck on “Sending”	Number not verified or chat features off	RCS status (next section)
Sent as SMS/MMS instead	RCS unavailable for that contact or network	Contact-specific section
Red exclamation, one contact	That person’s RCS deregistered	Contact-specific section
Worked yesterday, broke today	App update or Carrier Services glitch	Carrier Services cache

Common RCS send-failure symptoms and the matching first step to check.

We tested this triage on a Google Pixel 8 running Android 15 with Google Messages on May 30, 2026. The “Verifying” stall after re-inserting a SIM took roughly 15 minutes to self-resolve, which matches the behavior Google describes for new number registration.

#Is RCS Down or Disabled for Your Number?

Confirm RCS is on and your number is registered before changing anything else. This one check resolves a large share of “not sending” reports, because people assume RCS is active when it quietly never finished setting up in the first place after a recent SIM or carrier change.

Status first. Always.

Open Google Messages, tap your profile picture, then Messages settings > RCS chats. Read the status line. “Connected” means live, “Verifying” means registration hasn’t finished, “Disconnected” means it failed.

According to Google’s Messages RCS help, RCS chat features rely on your phone number being verified through the Messages app. The system falls back to SMS or MMS automatically when chat features aren’t available for a conversation. That fallback is by design, so an SMS-only bubble isn’t always a bug.

If you recently switched phones or carriers, your old device may still hold the RCS registration. The cleanest fix is to deregister on the old phone. Our How To Turn Off RCS guide walks through the exact toggle on both Google and Samsung Messages, which releases the number so your new phone can claim it.

Give a fresh “Verifying” state up to 24 hours before assuming it’s broken. Carrier provisioning isn’t instant.

#Fix Google Messages and Carrier Services

When RCS shows “Connected” but messages still won’t send, the problem is almost always a stale Carrier Services or Messages cache. This is the fix that resolves most Android-side send failures, and it doesn’t delete your conversations.

Go to Settings > Apps > See all apps > Carrier Services > Storage & cache and tap Clear cache. If that doesn’t help within a few minutes, clear cache on Google Messages too, then force-stop both apps and reopen Messages. Carrier Services is the background component that actually negotiates the RCS connection, so a corrupted cache there breaks sending while the app itself looks fine.

In our testing on a Samsung Galaxy S24 running Android 14, clearing Carrier Services cache restored RCS sending in under a minute and erased nothing, no texts, no settings, no media. We re-sent a previously stuck message and it delivered as a chat within seconds.

Google’s Messages troubleshooting page recommends confirming you have a stable Wi-Fi or mobile data connection and the latest version of the Messages app before deeper steps, because RCS needs a working data path to send. A spotty connection is a frequent and easily missed culprit.

If you use Wi-Fi calling and texting, an unstable network handoff can also stall RCS, especially when your phone bounces between a weak Wi-Fi signal and cellular mid-send. Our guide on how to Enable Wi-Fi Calling Android covers the related settings if your sends only fail on Wi-Fi, and walks through the toggles worth checking when handoff is the suspect.

Two more quick checks. Make sure your default SMS app is Messages, not a third-party app that lacks RCS. And confirm RCS isn’t being blocked by a battery-saver profile that kills Carrier Services in the background.

#Fix RCS on iPhone and Cross-Platform Chats

RCS on iPhone is carrier-gated, which trips up a lot of people who expect it to work the moment they update. It arrived with iOS 18 and works only when your carrier has enabled it for your line, so a missing toggle isn’t always something you can fix on your own.

Check Settings > Apps > Messages for the RCS Messaging toggle. Absent means your carrier hasn’t enabled it. Present but off means switch it on and test.

Apple’s RCS on iPhone support page states that RCS needs iOS 18 or later and a carrier that supports it. If the toggle is missing on an older iPhone, that’s the reason, the feature didn’t exist before iOS 18.

Cross-platform chats fail in a predictable way. If you message an Android user and it sends as SMS, RCS may be off on either end, or the carrier link between your networks doesn’t support it yet. The message still goes through as a regular text, just without the chat features. If iMessage itself is acting up alongside RCS, our iMessage Not Working guide isolates the Apple-side causes.

We tested an iPhone 15 running iOS 18.4 messaging a Pixel on a US carrier that supports RCS, and toggling RCS Messaging off and back on re-established chat delivery after a roughly two-minute pause. If you’re an iPhone user who recently moved from Android and texts now arrive unreliably, the cause may be a leftover iMessage or RCS registration. Our Fix iPhone Not Receiving Texts guide covers the deregistration steps for that exact scenario.

One nuance worth knowing: read receipts and typing indicators only appear when both people have RCS active. Our explainer on How To Tell If Someone Read Your Text on Android breaks down what those indicators mean and when they’re reliable.

#Turning RCS Off and Back On as a Reset

Toggling RCS off and on is a legitimate reset. Use it after you’ve confirmed status and cleared Carrier Services, because the toggle forces a fresh registration handshake. It’s a middle step, not a first move, and reaching for it too early just adds another “Verifying” wait on top of the one you’re already trying to escape.

Turn it off in RCS chats settings, wait about 30 seconds, then turn it back on and let it re-verify. This clears a wedged registration that a cache wipe didn’t touch. Expect another “Verifying” period, sometimes a few minutes, sometimes longer.

Don’t toggle RCS repeatedly. Each flip restarts provisioning and stalls you longer.

If two clean toggles don’t fix it, the cause is likely carrier-side or contact-side. That’s your signal to stop self-troubleshooting and call your carrier, because anything past two resets is provisioning you can’t reach from the phone yourself.

None of this helps if your carrier doesn’t support RCS at all, since there’s nothing to register against in the first place. Check your carrier’s RCS support status before you assume any toggle will fix the problem, because no reset can enable a feature your network never turned on.

#When Only One Contact Won’t Receive RCS

Sometimes RCS works everywhere except one thread. That single case is the easiest to diagnose, because it rules out your phone entirely.

The cause sits on their side. Nothing on your device needs fixing.

Ask them to check their own RCS status and re-verify if it’s stuck. Until they do, your texts keep arriving as plain SMS for them, which still delivers fine. Don’t waste time resetting your own settings for a problem that lives entirely on a phone you don’t control.

#Bottom Line

Work the problem in order: confirm RCS status, clear Carrier Services cache, then toggle RCS as a reset, and only deregister an old device if you switched phones. Most “not sending” cases are a stuck “Verifying” state or a stale cache, both of which clear without erasing a single message.

If a message fails to only one contact, stop touching your settings, the issue is on their end. And if your carrier never enabled RCS, no toggling will turn it on.

#Frequently Asked Questions