Google Messages creates unexpected multiple chat threads

What users are seeing in Google Messages

Since the latest rollout of the Google Messages app, a growing number of Android users have noticed that a conversation that once appeared as a single, continuous chat is now broken into two or more separate threads. The split occurs without any obvious action from the sender or receiver, and the new threads often contain only a handful of messages before the original chat resumes.

How the problem manifests

Conversation splitting explained

In a typical messaging experience, each participant in a chat is identified by a unique phone number or RCS identifier. The app groups messages that share the same identifier into a single thread. When the thread‑splitting bug activates, the app treats a subset of messages as belonging to a different identifier, even though the contact information has not changed. As a result, the user sees a new bubble at the top of the conversation list, labeled with the same contact name but a different thread.

Typical scenarios that trigger a split

• Receiving a group message that contains a mix of RCS and SMS content.
• Switching between Wi‑Fi and mobile data during an active conversation.
• Updating the app while a chat is open in the background.
• Using third‑party keyboards that insert invisible characters.

Technical background behind thread handling

Google Messages relies on the Rich Communication Services (RCS) protocol to deliver enhanced features such as read receipts, typing indicators, and high‑resolution media. RCS messages carry a chat identifier that the app uses to group related messages. When the identifier is missing, corrupted, or mismatched, the app falls back to the traditional SMS thread model, which is based solely on the phone number.

The recent update introduced a new logic path for handling mixed‑protocol messages. According to the Android Developers documentation on RCS, the system should reconcile identifiers automatically. However, an edge case appears to be triggering a mismatch, causing the app to create a new thread instead of appending the message to the existing one.

Why the change was not requested

Most Android users rely on a single, linear view of each conversation. Splitting a chat forces them to scroll between threads, search for missing messages, and sometimes resend information that was sent in the wrong thread. The issue is especially disruptive for business users who depend on a clear audit trail of communication.

Feedback collected on the Google Messages Help Center shows a surge in reports that the bug is affecting daily messaging habits. Users have expressed frustration that the problem appears after an automatic update, leaving them with limited control over the timing of the change.

Google’s official response

In a brief statement posted on the support page, Google acknowledged the thread‑splitting behavior and classified it as a “known issue” that is being investigated. The company promised a fix in an upcoming patch but did not provide a specific timeline. The statement also advised users to clear the app cache as a temporary measure, a recommendation that aligns with standard Android troubleshooting practices.

Workarounds and temporary fixes

1. Clear the app cache: Open Settings, navigate to Apps → Messages, and tap “Clear cache.” This forces the app to reload conversation data.
2. Disable RCS temporarily: Go to Settings → Chat features and turn off “Enable chat features.” This forces all messages to use SMS, which eliminates the identifier mismatch.
3. Reinstall the app: Uninstall Google Messages, restart the device, and reinstall from the Play Store. A fresh install often resets corrupted local data.
4. Use the web version: Access messages through messages.google.com on a desktop browser. The web client currently does not exhibit the same thread‑splitting behavior.

Comparisons with other messaging platforms

Apple’s iMessage and WhatsApp both maintain a single thread per contact, even when switching between data networks. iMessage, for example, uses a unique Apple ID to keep messages together, while WhatsApp relies on end‑to‑end encrypted sessions tied to the phone number. Neither platform has reported a similar split‑thread phenomenon in recent updates.

The difference highlights how Google’s reliance on a hybrid SMS/RCS model can introduce complexity. When a message fails to meet RCS criteria, the fallback to SMS may inadvertently trigger a new thread if the app does not correctly reconcile the two protocols.

What to expect in future updates

Industry analysts anticipate that Google will issue a hotfix within the next few weeks, given the volume of user reports and the impact on the app’s reputation. The fix will likely involve tighter validation of chat identifiers and a more robust fallback mechanism that preserves the original thread.

In the meantime, users who depend on a stable messaging experience should consider keeping the “Enable chat features” toggle off until the issue is resolved. While this removes some advanced RCS features, it restores the familiar single‑thread view that most users expect.

As Google continues to push RCS as the future of texting on Android, the company’s ability to handle edge cases like this will be a key factor in user adoption. A swift and transparent response will reinforce confidence in the platform and reduce the likelihood that users migrate to alternative messaging apps.