Unofficial archive. This is a read-only, community-run archive of the Apple Support Community. It is not affiliated with or endorsed by Apple Inc.

iOS 26.1 Bug: Auto-scrolling Stops Working in Messages

iOS 26.1 (23B85) fixed some previous bugs, but it also introduced a new one…


Now in the Messages app, when you type a reply in an EXISTING text message, auto-scrolling stops working after the 6th or 7th line of text (varies). NOTE: Auto-scrolling works fine when you are sending an initial text message, though.


I posted this issue on the Apple Feedback site. Anyone else experiencing this problem?

11 replies

This bug was just fixed with iOS 26.3. Yay! Thanks Apple!

Actually, I posted the following message on Feb 11, 2026...


"This bug was just fixed with iOS 26.3."

Happens to me too. It stops scrolling after the eighth typed line.


My work around: Once your text has disappeared off the bottom of the screen, manually swipe the text up until you can see your last typed word. The cursor should be there and blinking (if not, tap at the end of the word). You can then continue to type from there and the screen will scroll as normal for as long as you need.


Obviously a bug that, hopefully, someone on this forum will see and address in a future update.

That's really weird. It's fixed for me. Maybe try powering your phone down?

It's way worse when a photo is included. You have to scroll after every single line! With just text, after 8th line, you can scroll once and it seems to scroll automatically for awhile after that. Just updated today, and I hate this! I often include text at the same time as the photo. I don't want to send them separately.

Also once a picture or gif added to a message, auto scrolling is affected same way.

When will this get fixed?

I don't love this update but this bug is THE MOST DIFFICULT part of this newest update and I sincerely hope apple makes it a PRIORITY

This is HORRID. Apple please fix this!

Thank you for the heads up! I updated right away. So happy they fixed this!

This is still occurring for me and I have IOS26.3.