Google Messages users report scrolling issues when trying to view typed text

Many Google Messages users have been facing issues with the app for the past couple of days. I found plenty of reports online, especially on Google’s support forums suggesting that users can’t properly scroll through the text they are typing in the app.

Here’s how Paul Nittel, the OP who highlighted the problem 2 days ago, described the issue – “The app seems to “think” I want to edit the text, so it selects text, rather than scrolling up and down. Is this some weird setting that’s been altered? It worked fine earlier today.”

Their post now has over 60 votes from other users who claim that they’re also experiencing the same problem. Another user, Mary W 8676, said, “Once a text gets long enough for the lines to not fit in the field, they disappear under the keyboard and I can’t see what I’m typing and I can’t scroll down.”

The problem can be seen on various smartphones, including the likes of the Galaxy S23 and the Pixel 9. Judging by multiple comments on the thread, it seems like the standard troubleshooting tips like clearing the app’s cache or restarting the phone don’t seem to help at all. That said, since most reports about the problem started popping up a couple of days ago, it’s possible that it’s tied to a recent Google Messages update.

Interestingly, I have not been able to replicate the problem on my end on three separate Android phones, namely, the Pixel 8, Pixel 7a, and an Infinix GT 20 Pro. Initially, I tested it with the latest beta, however, I also installed the latest stable version on the Pixel 8 but couldn’t reproduce the bug. A team member also couldn’t reproduce it on their Pixel 8 Pro with Google Messages version 20250225_OO. So my best guess here is that the issue is affecting a limited number of users.

If the problem is a headache for you, then you could try dabbling in the beta channel for the time being. To do this, you need to go to the Play Store, search for Google Messages, open its informational page, scroll down, and choose to become a beta tester. Once done, you will likely see an option to update the app. So go ahead and install the update, then check to see if the bug persists.

Just note that the potential workaround mentioned above is based on my own assumptions given my testing. It’s not a guaranteed fix. Nevertheless, it might be worth giving a shot. For those who can live with the bug, it’s best if you wait for the next stable update which could arrive in the next few days or so.

Let me know if the beta helped restore normal functionality in the comments below!