Google Messages Bug Can Attach Old Texts to New Chats

Some Android users have reported a serious Google Messages privacy problem: text from an old, unrelated conversation can appear alongside a newly written message and, in some cases, be sent to the new recipient. Reports involve both SMS and RCS messages, making the risk especially concerning when old conversations contain personal or sensitive information. 57

What the bug does

The reported behavior is not simply a message being sent to the wrong contact. Instead, Google Messages may retrieve text previously sent in one conversation and attach it to a new message being prepared for someone else. In some cases the old text is visible before sending; in others, users say it was delivered to the unintended recipient. 312

Reported messages can date back months or years. One recent report described a message sent to an asphalt company that included a vulgar text originally sent to the user's wife more than a year earlier. Reports were still appearing on September 7 while Google's fix was rolling out. 2

This is a privacy issue because the resurfaced content can be unrelated to the current conversation and may expose information the sender never intended to share with that recipient.

What Google has confirmed

Google publicly acknowledged the issue on September 2, 2026. A spokesperson said: “We’re currently rolling out a fix that will reach everyone over the coming weeks. Please ensure you stay up to date with the most recent version of Google Messages.” 8

The rollout is gradual, rather than an immediate fix for every device. Coverage published after the announcement indicated that reports were continuing, so an app update may not eliminate the problem immediately for every affected user. 215

Is a phone transfer the cause?

Available reporting links the issue to some users who transferred data to a new phone. However, the exact technical cause, the affected Google Messages versions, and the reason only some users appear to be affected have not been publicly explained. 15

That distinction matters: a transfer is a reported trigger or association, not a confirmed root-cause diagnosis. Likewise, the reports do not establish that a particular phone brand, RCS setting, or Android version is solely responsible. The issue has been reported across both SMS and RCS. 47

Should you join the beta program for the fix?

The available reports do not establish that Google Messages beta users will reliably receive this specific fix before stable-channel users. Since Google has said the fix is rolling out over coming weeks, the practical step is to install the latest available Google Messages update rather than enroll in beta solely for this issue. 815

What to do while the rollout continues

1. Update Google Messages. Check the Play Store for the newest version, as Google specifically advised users to stay current. 8
2. Review the complete message and recipient before sending. If unfamiliar older text appears in the compose area, do not send it.
3. Use another trusted channel for highly sensitive information until the issue stops. This is a precaution, not a confirmed workaround.
4. Document and report the behavior. Google has asked at least one affected user for screenshots and an in-app feedback report, which can help its investigation. 12
5. Treat common troubleshooting steps cautiously. Reports indicate that clearing cache, restarting the phone, toggling RCS, and reinstalling the app have not consistently resolved the problem. 14

A factory reset should not be the default response. Although some users have reported it helped, it is a disruptive measure with data-loss risk and is not presented by Google as the official fix. 6

Bottom line

The core risk is unintended disclosure: an old message from one chat may be appended to a new message for someone else. Google has acknowledged the problem and says a fix is rolling out, but the rollout may take weeks. Until the updated behavior is confirmed on an affected device, keep Google Messages updated and inspect every outgoing message—especially messages containing private details. 815