iOS 26 rendering gap on scroll surfaces — lower scroll view does not render

On iOS 26 (26.0–26.5), a rectangular region in the lower half of the screen sometimes does not render while the content underneath remains laid out and interactive — scrolling works, hit testing succeeds, and rows visibly emerge from behind the floating tab bar as you scroll. This is a render-server / compositor gap, not a layout or safe-area issue.

We see it on both UIKit and SwiftUI scroll surfaces inside the same UITabBarController:

UIKit: UICollectionView with UICollectionViewFlowLayout (sectionInsetReference = .fromSafeArea)

SwiftUI: List(.plain) nested in TabView(.page) inside a UIHostingController

Confirmed on iPhone 16 Pro, iPhone 17 Pro, iPhone 13 Pro Max. Community threads (linked below) report the same symptom in Messages, Notes, Safari, Mail, and the App Store.

Questions for Apple

Is this acknowledged as an OS-level regression, and is a fix targeted for an upcoming iOS 26.x release?

Is there a deterministic repro? We've tried background/foreground cycles, push notifications mid-scroll, tab switches during inertia, lock/unlock, orientation flips, simulated memory warnings, layout-invalidation storms, and trait-collection cycles — none reliably trigger it on our test devices.

Is there a developer-side mitigation (e.g. avoiding specific UIVisualEffectView / Glass configurations, opting out of a rendering optimization) until a system fix lands?

Is there a runtime signal on CALayer or UIScrollView we can inspect to detect this gap state and force a recovery (tile redraw, backing-store discard, etc.)?

Notes

We cannot reproduce locally. Affected users hit it organically; once it appears it persists across re-layout until the view controller is torn down.

Community reports consistently mention Reduce Transparency being enabled on affected devices, and toggling it off clears the issue for many. In our own testing, RT alone is not sufficient to trigger the bug — it appears to be a contributing condition rather than the trigger.

References:

Apple Discussions: https://discussions.apple.com/thread/256182149

Reddit r/ios (multiple system apps): https://www.reddit.com/r/ios/comments/1nlzn7f/some_apps_cutting_off_half_the_display/

https://www.idownloadblog.com/2026/03/23/webpage-content-cutting-off-safari/

Thank you for your post.

A portion of the screen failing to render is definitely not a great user experience, so it's important we find out exactly what's going on here and how to resolve it.

I'll do everything I can to help us narrow this down and get it in front of the right team. 😃

We see it on both UIKit and SwiftUI scroll surfaces inside the same UITabBarController:

Since you mentioned you're unable to reproduce this locally, it would be helpful to gather as much detail as possible from the affected users for each of these apps

That Apple Discussions thread has varying reports, with some users mentioning they were mid-search, while users in the Reddit thread report the issue is resolved by disabling Reachability.

Once we narrow this down, I want to make sure I see exactly what you are seeing. Please file a bug report with Feedback Assistant and attach your project, screenshots, and steps to reproduce there as well, so I can share it with the relevant engineering team.

Share the Feedback ID with me here once you've filed it, and I'll pass the report along to the relevant engineering team

report the same symptom in Messages, Notes, Safari, Mail, and the App Store.

Are you able to reproduce any of these yourself, including the Safari example you linked from iDownloadBlog? If so, please create a corresponding report for each. I'd be interested in sharing these reports with the appropriate team for each situation.

Thank you again!

 Travis

Feedback Assistant report submitted - FB22837072

We have not been able to reproduce ourselves but get frequent TestFlight feedback about it. Note that often content is still rendered below the gap behind the tab bar, indicating it's not a simple content inset issue

iOS 26 rendering gap on scroll surfaces — lower scroll view does not render
 
 
Q