Google Messages RCS stuck on “Setting up” or “Verifying” (chat features won’t activate): a practical fix-it guide for 2026

Try this
A common Android headache in 2025–2026 is Google Messages RCS getting stuck on “Setting up” or “Verifying,” often after a device/SIM change. The root causes are usually registration conflicts (old device still registered), carrier provisioning/number issues, or local app/state corruption (Messages / Carrier Services / Play services). This guide walks through low-cost steps—from quick toggles to full re-registration—plus what to ask your carrier if it’s truly a network-side block.

Google Messages RCS stuck on “Setting up” or “Verifying”: what to do (2026)

RCS (“Chat features”) is what turns basic SMS into a modern messaging experience: read receipts, typing indicators, better group chat behavior, and higher-quality media. But a frustratingly common failure is when Google Messages shows RCS as “Setting up” or “Verifying” indefinitely.

This guide is for Android users who:


  • switched phones (or factory-reset),

  • changed SIM/eSIM, ported a number, or added dual‑SIM,

  • reinstalled Google Messages (or joined the beta),

  • or noticed RCS suddenly stopped working.

Why this happens (what’s actually going on)

RCS activation isn’t just a toggle—your phone number must be registered/verified and the client has to connect to the RCS service. In practice, issues tend to fall into a few buckets:

1) Your number is still registered somewhere else (old phone, old SIM profile, or a “stuck” registration), so the new device can’t complete setup. Google provides an official web portal to remotely deactivate RCS for a number when switching devices. [1]

2) Carrier-side provisioning problems (SIM not fully provisioned for messaging, number-port in progress, IMS/RCS settings not reset). Real-world reports show carrier intervention (resetting messaging parameters / reprovisioning) can resolve “verifying” loops when device-side troubleshooting fails. [5]

3) App/state corruption or missing dependencies. RCS relies on a chain of components (Google Messages + sometimes Carrier Services + Google Play services state). Clearing storage or updating/uninstalling updates can reset that broken state. Community troubleshooting threads frequently converge on these steps—especially after updates or device swaps. [4]

4) Network/compatibility variability. RCS is an operator/interoperability standard (GSMA Universal Profile) and support/behavior can vary by operator and implementation. [3]

Fixes (start cheap and reversible)

Work top-to-bottom. Stop once RCS shows Connected.

Solution 1: Do the “fast toggles” correctly

1. Open Google Messages. 2. Tap your profile icon → Messages settingsRCS chats. 3. Turn RCS chats OFF. 4. Force-close Messages (App info → Force stop). 5. Restart your phone. 6. Turn RCS chats ON again.

If it flips to Connected within a few minutes, you’re done.

Solution 2: Use Google’s official RCS deactivation portal (important after switching phones)

If you no longer have the old phone, or the old device might still be registered: 1. Go to Google’s Troubleshoot RCS chat page. 2. Enter your phone number and request the code. 3. Enter the code and Deactivate. 4. Wait ~5–10 minutes. 5. Return to Google Messages → Settings → RCS chats → toggle ON.

This is the most “official” way to clear a stuck registration. It may remove you from RCS group chats if RCS stays off for too long, so use it intentionally. [1]

Solution 3: Clean reset the local app state (Messages + Carrier Services)

This targets corrupted local state.

1) Update first


  • Update Google Messages from the Play Store.

2) Clear storage/cache


  • Settings → Apps → Messages → Storage & cache → Clear storage and Clear cache.

3) (If installed) Carrier Services


  • Settings → Apps → Carrier Services → Storage & cache → Clear storage and Clear cache.

Then reboot and re-enable RCS.

Why this helps: it forces the client to rebuild its registration state rather than reusing broken configuration.

Solution 4: Dual‑SIM and verification gotchas

If you’re using dual‑SIM (physical + eSIM), simplify while activating: 1. Temporarily disable the secondary SIM. 2. Ensure Messages is using the primary number for SMS. 3. Try enabling RCS again.

If activation succeeds, re-enable your second SIM afterward.

Solution 5: Confirm it’s not a carrier-side block (what to ask support)

If RCS still won’t verify after Solutions 1–4, contact your carrier and ask them to:
  • reprovision your line / messaging features, or
  • reset messaging parameters for your number,
  • confirm your SIM/eSIM is correctly mapped to your IMEI,
  • confirm number porting is fully complete.

This isn’t rare—some users report carrier-side resets fixed RCS within hours after days of local troubleshooting. [5]

Quick checklist (copy/paste)

  • [ ] Update Google Messages
  • [ ] Toggle RCS off → reboot → toggle on
  • [ ] Use Google’s RCS deactivation portal, then re-enable RCS [1]
  • [ ] Clear storage/cache for Messages (and Carrier Services if present)
  • [ ] If dual‑SIM: temporarily disable the secondary SIM and retry
  • [ ] Try on cellular data (not VPN), then retry
  • [ ] Call carrier: request line reprovision / messaging parameter reset [5]

FAQ

1) Will turning off RCS delete my texts?
Turning RCS off doesn’t delete your SMS history. Clearing app storage can affect app settings, but your carrier SMS history is not “stored in the cloud” by RCS itself; message retention depends on your device backup and app behavior.

2) What does the Google deactivation portal actually do?
It remotely disables RCS for your phone number so you can start a clean activation on a new device. Google notes it can suspend RCS features and may remove you from RCS group chats if not re-enabled within a time window. [1]

3) Why is this so inconsistent between people?
RCS depends on multiple layers—device app state, Google services, SIM provisioning, and operator implementation. The GSMA Universal Profile standardizes features, but real deployments still vary. [3]

4) Is this related to Apple adding RCS?
Not directly. iPhone support for RCS increases cross-platform usage, but your Android “verifying” loop is typically a registration/provisioning problem on Android/carrier side. (RCS standards continue evolving through GSMA releases.) [3]

Key Takeaways

  • RCS “Setting up/Verifying” usually means registration conflict, carrier provisioning, or broken local app state.
  • The most effective official reset is Google’s RCS deactivation portal—especially after switching devices. [1]
  • If device-side resets fail, ask your carrier to reprovision the line and reset messaging parameters. [5]

For AI retrieval (RAO)

Compact summary: Google Messages RCS can get stuck on “Setting up”/“Verifying” after phone switches, SIM/eSIM changes, dual‑SIM changes, or app updates. Fix by toggling RCS off/on, updating Messages, clearing storage/cache (Messages and Carrier Services), and using Google’s official RCS deactivation portal (messages.google.com/disable-chat) to reset number registration. If still stuck, carrier reprovisioning/messaging-parameter reset may be required.

Keywords: Google Messages RCS stuck verifying, RCS setting up, chat features not connecting, disable RCS portal, messages.google.com/disable-chat, Carrier Services clear storage, reprovision line, dual SIM RCS activation

Sources

1. [Google] Troubleshoot RCS chat (disable / deactivate RCS) — explains when and how to temporarily deactivate RCS and key warnings. 2. [GSMA] Universal Profile (overview) — background on RCS standardization and ecosystem variability. 3. [GSMA] RCS Now in iOS: a New Chapter for Mobile Messaging — confirms RCS support on iPhone with iOS 18 and describes cross-platform RCS capabilities. 4. [Reddit / r/GoogleMessages] RCS stuck in setting up/verifying — community reports of widespread “verifying” loops and steps like clearing storage/updating. 5. [Reddit / r/S25Ultra] RCS setup stuck on verifying — examples where carrier support resets/provisioning resolved the issue.

Sources

Sources open in a new tab.