Google Messages 'Message Not Sent' Error on Android: Fix It Fast

You hit send, the little bubble turns red, and Google Messages slaps a 'Message Not Sent' tag under it. Tapping the bubble gives you a 'Resend' option that fails again. Cool.

What's actually happening here is one of two things: either your carrier's SMS gateway rejected the message (classic SMS), or RCS — Google's fancy chat layer — lost its data handshake with the Jibe servers. Those two failure modes look identical in the UI, which is why generic 'restart your phone' advice feels useless. The fixes below are ordered by how likely they are to work without wasting your afternoon.

Fix 1: Toggle Airplane Mode (30 seconds)

This clears a stale radio registration with your carrier. It sounds cliché because it works.

1. Swipe down the notification shade.
2. Tap Airplane Mode. Wait 15 seconds. Tap it again.
3. Wait for the signal bars to come back, then tap the failed message and hit Resend.

If the message goes through, you're done. Don't read further unless it comes back tomorrow.

If it still fails, that tells you something important: this isn't a transient network blip. Either the recipient's number is bad, or something on your phone is actively blocking outbound SMS/RCS.

Quick sanity check before moving on

• Send a test text to yourself (your own number). If that fails too, the problem is 100% on your side.
• Check the recipient's number — the leading zero issue on international numbers trips people up constantly. If you're texting a UK number from the US, it needs +44 and no leading zero.
• Look at the message bubble. A green outline means SMS/MMS. Blue means RCS. Note which one is failing.

Fix 2: Verify RCS and APN Settings (5 minutes)

Google Messages defaults to RCS when both parties support it, and RCS has its own state machine that breaks independently of SMS. The telltale sign: SMS works, but the blue chat bubbles fail with 'Message Not Sent' or hang on 'Sending...' forever.

If RCS is the problem

1. Open Google Messages.
2. Tap your profile picture (top right) → Messages settings.
3. Tap RCS chats.
4. Toggle Turn on RCS chats off. Wait 30 seconds. Toggle it back on.
5. Watch the status line. It should say 'Connected.' If it sits on 'Setting up...' or 'Trying to verify...', your carrier's RCS provisioning is the issue.

The reason step 4 works is that toggling RCS re-runs the Jibe registration handshake. If that handshake stalls, Messages falls back to SMS but keeps the failed RCS bubble red on your screen — which is what you've been staring at.

After re-enabling RCS, the verification can take up to 10 minutes on some carriers (looking at you, T-Mobile MVNOs). Give it time before declaring defeat.

If SMS/MMS is the problem (green bubbles fail)

Your APN (Access Point Name) settings are probably wrong or stale. This happens after a carrier update, after swapping SIMs, or after installing a custom ROM.

1. Settings → Network & internet → SIMs → pick your SIM.
2. Tap Access Point Names.
3. Tap the three-dot menu → Reset to default.
4. Reboot.

If 'Reset to default' isn't there (some OEM skins hide it), tap your active APN, screenshot every field first, then re-enter the values from your carrier's support page. Carriers publish these — search '[carrier name] APN settings' and match the MMS proxy and MMSC fields exactly. A single typo in the MMSC URL breaks MMS while leaving SMS fine.

Fix 3: Clear Messages Data and Re-verify (15+ minutes)

This is the nuclear option. It wipes local message state — your conversation list survives (it's in Google's cloud or your SMS database), but any pending sends and RCS registration are gone. Do this only after Fix 1 and Fix 2 fail.

Step A: Clear cache, then data

1. Settings → Apps → Messages.
2. Tap Storage & cache.
3. Tap Clear cache first. Test sending. If it works, stop.
4. If not, go back and tap Clear storage. Confirm.

Reopen Messages. You'll be asked to set it as your default SMS app again. Do that, then open the app and let it re-sync. On a large message history this can take 5–10 minutes.

Step B: Deregister and re-register RCS

If RCS still shows 'Setting up...' after clearing storage, your number is stuck in Jibe's registration registry. This is common after porting your number to a new carrier — Jibe still thinks the old carrier owns it.

Open a browser and go to messages.google.com/disable-chat. Sign in with the same Google account. Enter your phone number. This force-unregisters RCS. Wait 10 minutes, then go back into Messages → Settings → RCS chats and re-enable. The handshake should complete.

Step C: Check the default SMS app

Some third-party apps (looking at you, Samsung Messages on older One UI builds, and certain MDM-managed enterprise apps) silently claim the SMS role and intercept outbound messages, then fail to deliver them. Confirm under Settings → Apps → Default apps → SMS app that Google Messages is selected.

When none of this works

If you've done all three fixes and messages still fail, the problem is upstream of your phone:

• Carrier-side SMS block. Some prepaid plans or newly activated lines have outbound SMS throttled or disabled until the account fully provisions. Call support and ask them to check the SMS feature flag on your line.
• Recipient-side block. If only one person's messages fail, they've blocked you. The 'Message Not Sent' is your phone's way of not telling you that.
• Physical SIM damage. Rare, but a SIM that's been cut down or has oxidized contacts will fail outbound SMS while voice calls work. Swap it at a carrier store — usually free.

Ninety percent of 'Message Not Sent' cases resolve at Fix 1 or Fix 2. If you're in the other ten percent, it's almost always the RCS registration being stuck after a number port — and messages.google.com/disable-chat is the specific tool that fixes it.