Setting up a new Android phone should be routine. For a growing number of Google Messages users, it has triggered something far more unsettling — old texts from unrelated conversations resurfacing inside new threads and, in some cases, firing off to the wrong person entirely. Verification codes, intimate messages, private exchanges you’d never want a stranger to receive. According to Android Authority and corroborated by PhoneArena, this is not a hypothetical. The bug is real, Google has confirmed it, and the fix is still weeks away.
What’s Actually Happening
Old texts are crossing conversation threads — and in some cases, reaching people who were never meant to see them.
Reports emerged across Reddit and Google’s own community channels, with users on Pixel and Samsung devices flagging the problem independently. It hits SMS and RCS conversations alike, so switching message types won’t protect you. Multiple outlets — including Android Authority and Frandroid — have confirmed the scope extends across device brands, not just one manufacturer.
Here’s what the reporting shows so far:
- The bug appears most commonly after transferring data to a new phone, per Google’s statement to Android Authority
- Affects Pixel and Samsung devices; not isolated to one brand
- Impacts both SMS and RCS conversations
- Standard fixes — clearing the cache, toggling RCS, reinstalling the app — have not reliably worked for most users; these rank among the most frustrating computer problems users face
- A factory reset reportedly helped some users, but only when old messages were not restored afterward
What Google Says – And What To Do Right Now
Google has acknowledged the issue and says a fix is rolling out, but the timeline leaves users exposed in the meantime.
“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,” a Google spokesperson told Android Authority.
Google collected details from at least one affected user and forwarded them to its engineering team. This is being treated as an active product issue, not isolated user error.
Until that fix reaches your device, avoid sending anything sensitive through Google Messages — much like how confidential files exposed through platform-level failures can spiral quickly. If an unintended text already escaped, use the app’s delete-for-everyone option immediately — it’s the digital equivalent of frantically recalling a company-wide email, damage control rather than a guarantee. To stay safe, no reliable DIY workaround exists right now.
If Google’s patch lands cleanly, this becomes a reputational bruise and a hard lesson in migration testing. If it doesn’t, Google owes users a proper root-cause explanation — not just a reminder to update their app.
