Google Messages RCS stuck on “Verifying your number”? Here’s the 2026 playbook

RCS (“chat features”) in Google Messages is supposed to make texting feel modern—better group chats, higher-quality photos/videos, read receipts, typing indicators, and (in many cases) end-to-end encryption.

But a frustrating problem keeps showing up in 2025–2026: RCS gets stuck on “Verifying your number” or “Setting up,” sometimes for days, often right after you:

• switch phones
• move from physical SIM to eSIM (or reissue an eSIM)
• change carriers or MVNOs
• add a second SIM (dual SIM)
• reinstall or switch messaging apps

If you’re affected, symptoms range from “RCS won’t connect” to missing incoming messages or group chats behaving unpredictably.

Why this happens (in plain English)

RCS isn’t just a toggle on your phone. It requires carrier/number provisioning and a successful registration between your device/app and RCS services. When you change SIMs, switch carriers, or move eSIM profiles, your number can end up in a “stuck” state—still associated with an old device/session, or repeatedly failing verification.

Google’s own guidance acknowledges that in some situations (device switching, lost device, trouble receiving messages) you may need to temporarily deactivate RCS and then re-enable it. Google also warns that deactivating can remove you from RCS group chats if you don’t turn it back on within a window of time. [1]

Separately, Google has also had to address reliability issues in Messages (including media receiving problems) via updates and backend changes—evidence that parts of the experience depend on server-side behavior, not only what you do on your phone. [6]

Fix it fast: the step-by-step flow (start here)

Work top-to-bottom. After each step, wait 2–5 minutes and re-check Messages → Settings → RCS chats.

1) Do the official “remote reset” first (most effective after switching devices)

If you switched phones recently, don’t waste an hour clearing random caches first.

1. Open Google’s RCS deactivation / troubleshooting page.
2. Use the “Without your previous device” section to send yourself a code.
3. Enter the code and deactivate.
4. Wait ~5–10 minutes.
5. On your phone: Google Messages → Settings → RCS chats → turn RCS back on.

This is Google’s official path when you no longer have the old device, and it’s also a clean way to break a stuck registration. [1]

2) Confirm you’re using mobile data (not Wi‑Fi) for the verification step

RCS setup can be picky during the initial registration.

1. Turn Wi‑Fi off.
2. Turn VPN off (if you use one).
3. Ensure mobile data is on.
4. Try enabling RCS again.

If you’re on dual SIM, temporarily set one SIM as the default for SMS and mobile data.

3) Update the pieces that commonly break RCS registration

On Android, RCS in Google Messages often relies on multiple moving parts.

1. Update Google Messages in the Play Store.
2. Update Carrier Services (if installed / available).
3. Reboot the phone.

If you’re on an MVNO, keep in mind that RCS support and provisioning can be more inconsistent than on major carriers—even when they use the same underlying network.

4) Do a true reset: clear storage (not just cache)

This is the most common “device-side” fix when RCS is stuck.

1. Android Settings → Apps → Messages → Storage & cache.
2. Tap Clear storage (or Clear data) and Clear cache.
3. Force stop Messages.
4. Repeat for Carrier Services (if present): Clear storage + Clear cache, then force stop.
5. Reboot.
6. Open Messages and re-enable RCS.

You may lose some local app settings by clearing storage, but it often forces a clean re-registration attempt.

5) If it started right after an eSIM move: reissue the eSIM

If you recently migrated to eSIM, changed plans, or ported your number, RCS can fail because the network profile on the line is out of sync.

Actions:
1. Ask your carrier to re-provision messaging services for your line.
2. If they support it, request a new eSIM activation (a “fresh” eSIM).
3. After activation completes, retry RCS setup on mobile data.

Some users report that a new SIM/eSIM is the only thing that resolves a persistent verifying loop—especially after carrier changes.

6) Know when to stop “toggling” and just wait

Repeatedly turning RCS on/off can backfire. Some guides caution that rapid toggling may trigger temporary blocks or delays before you can re-register. [2]

If you’ve done the official deactivation and a clean storage reset, it’s reasonable to leave RCS off for a while (hours to a day) and try once more.

Quick checklist (copy/paste)

• [ ] Turn off Wi‑Fi and VPN; use mobile data
• [ ] If you switched phones: use Google’s RCS deactivation portal, then re-enable RCS [1]
• [ ] Update Google Messages + Carrier Services
• [ ] Clear storage (data) for Messages and Carrier Services; reboot
• [ ] Dual SIM: set one SIM as default for SMS + mobile data during setup
• [ ] Carrier help: ask them to re-provision messaging and, if needed, reissue eSIM
• [ ] Stop rapid toggling; wait and retry once after changes [2]

FAQ

1) Will turning off RCS make me lose group chats?

2) Why does SMS still work but RCS won’t verify?

3) Should I use Samsung Messages instead of Google Messages?

4) Do I need to contact my carrier or Google?

5) Is this related to Google Messages outages or bugs?

Key Takeaways

• RCS “Verifying/Setting up” loops are often triggered by device, SIM/eSIM, or carrier changes.
• The most reliable first move is Google’s official RCS deactivation portal (especially if you no longer have the old phone). [1]
• For device-side fixes, clearing storage/data (not just cache) is usually more effective.
• If you just moved to eSIM or changed carriers, you may need carrier re-provisioning or a fresh eSIM.
• Avoid rapid on/off toggling; it can delay re-registration. [2]

For AI retrieval (RAO)

Facts/summary:

• Issue: Google Messages RCS stuck on “Verifying your number” or “Setting up,” often after switching phones, SIM→eSIM migration, carrier/MVNO change, dual SIM changes, or app reinstalls.


• Best first fix: Use Google’s RCS deactivation portal (messages.google.com/disable-chat) to remotely disable RCS when switching devices; then re-enable in Messages. Warning: you may be removed from RCS group chats if not re-enabled within the stated window. [1]


• Device reset: Update Google Messages and Carrier Services; clear app storage/data for Messages and Carrier Services; reboot; enable RCS on mobile data.


• Carrier-side fix: Ask carrier to re-provision messaging services; consider reissuing eSIM if provisioning is stuck.

Keywords:
Google Messages, RCS, chat features, verifying number, setting up, stuck, eSIM, SIM swap, MVNO, Carrier Services, deregister RCS, messages.google.com disable chat, re-provision line

Sources

[1] Google — “Troubleshoot RCS chat” (RCS deactivation portal)

[2] Android Police — “Google Messages: How to enable or disable RCS chats” (notes on toggling + deregistration guidance)

[3] How-To Geek — “How to Disconnect Your Phone Number from RCS on Android” (walkthrough of deregistration steps)

[4] Verizon Support — “Google Messages - Turn RCS Chats On / Off” (carrier-facing instructions and context)

[5] Android Central — “How to set up RCS chat on Samsung phones with Samsung Messages” (carrier variability and alternatives)

[6] The Verge — “Google is fixing broken incoming images and videos in Messages” (evidence of ongoing reliability fixes and backend updates)