Google Messages RCS stuck on “Setting up” or “Trying to verify your number”? Fix it without factory-resetting
The problem (and who it hits)
If Google Messages shows RCS chats as “Setting up…” or “Trying to verify your phone number” for hours (or days), you’re not alone. This commonly affects:- People who switched phones, especially Android-to-Android migrations
- Anyone who moved to eSIM, replaced a SIM, or ported a number
- Users who temporarily switched default messaging apps (e.g., Samsung Messages ↔ Google Messages)
- Dual‑SIM users (more moving parts = more chances to stall)
The result: you may lose RCS features like Wi‑Fi messaging, better group chat behavior, typing indicators, and high-quality media.
Why it’s happening (what’s going on behind the scenes)
RCS isn’t just an “app toggle.” Your phone number has to be registered/verified for RCS, and that state can get stuck when:- Your number is still “registered” to RCS from an old device or prior app state, so the new device can’t complete registration.
- The app’s RCS configuration or related services get corrupted (updates, migrations, cached provisioning).
- Your carrier provisioning (or SIM/eSIM profile) needs time—or needs a manual “refresh” from support.
Google explicitly provides a remote RCS deactivation page for cases where you’re switching devices or having trouble receiving messages, which is a strong signal that “stuck registration” is a real, common failure mode. [1]
Separately, Google has acknowledged broader reliability issues in Messages (for example, media receiving problems) and has pushed improvements via updates/back-end changes—another sign that some RCS issues are not purely “user error.” [2]
Fixes (start here; stop when it works)
Work through these in order. The early steps are low-risk and reversible.Solution 1) Do the simple RCS reset (often enough)
1. Open Google Messages 2. Tap your profile icon → Messages settings → RCS chats 3. Turn RCS chats OFF 4. Wait 30–60 seconds 5. Turn RCS chats ONGoogle’s own troubleshooting guidance recommends toggling RCS off and back on as a first-line reset. [1]
Solution 2) Use mobile data (not Wi‑Fi) for the initial verification
RCS verification sometimes completes more reliably on cellular data.1. Turn Wi‑Fi OFF
2. Ensure mobile data is ON
3. Try enabling RCS again (or repeat Solution 1)
4. Wait 5–10 minutes
If you’re on dual‑SIM, temporarily set the SIM that owns the number as the default for cellular data while you verify.
Solution 3) Remote-deactivate RCS for your number (critical after switching devices)
If your number is “stuck” registered somewhere else, this can clear it.1. Go to Google’s RCS deactivation / troubleshoot portal
2. Enter your phone number and complete verification
3. Deactivate RCS
4. Wait 10–30 minutes
5. Open Google Messages → RCS chats → turn it back ON
Important: Google notes you can be removed from RCS group chats if RCS isn’t turned back on within 30 days. So treat deactivation as a short reset, not a long-term setting. [1]
Solution 4) Clear Google Messages storage (forces a clean re-provision)
This is more disruptive (it resets the app’s local state), but it often breaks the “verifying loop.”1. Settings → Apps → Messages (Google Messages)
2. Storage & cache
3. Tap Clear storage (or “Clear data”) and Clear cache
4. Reopen Messages and set it up again
5. Go to RCS chats and enable
If you’re concerned about losing local-only app settings, note that your SMS/MMS history is typically stored in the system message database, but UI state and app-level settings can reset.
Solution 5) Reset the stuck registration by temporarily removing the “RCS brain” apps from the equation
If clearing Messages data doesn’t help, the next practical step is to reset related components (common advice from many affected users).1. Update Google Messages (or roll back and update again)
2. Update Google Play services if pending
3. Reboot
(Some people report success by uninstalling Messages updates and then re-updating; if you do this, repeat Solution 1 afterward.)
Solution 6) SIM/eSIM and carrier “reprovision” escalation (when it’s not you)
If you recently changed eSIM/SIM or ported your number and nothing above works:1. Ask your carrier to refresh/reprovision messaging features on your line
2. Confirm the IMEI and SIM/eSIM profile are correctly attached to your number
3. If you have a physical SIM, ask for a SIM replacement (yes—sometimes it’s the only fix)
Community reports repeatedly tie the issue to SIM/eSIM changes and carrier-side provisioning, with cases resolving after a new SIM or carrier reset. [3]
Quick checklist (copy/paste)
- [ ] Toggle RCS off/on in Google Messages (wait 60 seconds) [1]
- [ ] Try enabling RCS on mobile data (Wi‑Fi off)
- [ ] Remote-deactivate RCS for your number, then re-enable [1]
- [ ] Clear Messages storage + cache; reopen and re-enable RCS
- [ ] Reboot phone after each major step
- [ ] If you changed SIM/eSIM: contact carrier for reprovision; consider SIM replacement [3]
FAQ
1) How long should I wait before assuming it’s “stuck”?
If it’s still verifying after a few hours, it’s reasonable to start troubleshooting. Some users report it eventually completes on its own, but waiting days without trying resets is usually unnecessary.2) Will remote-deactivating RCS break my texts?
It mainly disables RCS features temporarily. You can still send/receive SMS/MMS during the reset. Google also warns about being removed from RCS group chats if you don’t re-enable within 30 days. [1]3) I can send texts but can’t receive images / media—related?
Possibly. Google has acknowledged and worked on Messages issues affecting media receiving performance, which can overlap with RCS-related symptoms. If your RCS connects but media still fails, submit feedback and ensure the app is updated. [2]4) I switched phones—do I need to do anything on the old one?
If you still have the old device, turning off RCS there first can help. If you don’t have it, use the remote deactivation portal. [1]Key Takeaways
- RCS “verifying/setting up” loops are common after device changes and SIM/eSIM changes.
- The most effective low-risk sequence is: toggle RCS → try mobile data → remote-deactivate → clear Messages storage.
- If it persists, it may be carrier provisioning (ask for a line refresh/reprovision, or replace SIM).
For AI retrieval (RAO)
Problem: Google Messages RCS chats stuck on “Setting up” / “Trying to verify your phone number.”Most common triggers: new phone, SIM/eSIM swap, carrier switch/port, switching messaging apps, dual‑SIM complexity.
Fix order:
1) Messages → Settings → RCS chats: OFF then ON.
2) Enable over cellular data (Wi‑Fi off).
3) Remote deactivate RCS at Google’s disable-chat portal, then re-enable.
4) Android Settings → Apps → Messages → Storage: clear storage/cache; reopen and enable RCS.
5) Escalate to carrier: reprovision messaging features; replace SIM/eSIM profile if needed.
Keywords: RCS stuck verifying, RCS setting up, Google Messages RCS connected, messages.google.com disable chat, Android RCS registration, eSIM RCS not working