React Navigation 6.x, 7.x, in iPad iOS 26.1, scrollview, flatlist... always scroll to top when back from another screen

[ZaneRH]

Current behavior

With React Navigation 6.0
In iPad iOS 26.1, the scrolled down scrollable view always auto scroll back to top, when navigation.goBack() from another screen.
The screens are inside a Stack Navigator, with { headerShown: false } in screenOptions.
With any header related options set, the problem will occur.
It's fine when the default header is shown (no headerShown / header set in screenOptions)

Expected behavior

Should not scroll to top when back from another screen.

Reproduction

Platform

• Android
• iOS
• Web
• Windows
• MacOS

Packages

• @react-navigation/bottom-tabs
• @react-navigation/drawer
• @react-navigation/material-top-tabs
• @react-navigation/stack
• @react-navigation/native-stack
• react-native-drawer-layout
• react-native-tab-view

Environment

• [] I've removed the packages that I don't use

package	version
@react-navigation/native	6.1.9
@react-navigation/bottom-tabs	6.5.20
@react-navigation/drawer
@react-navigation/material-top-tabs
@react-navigation/stack	6.3.20
@react-navigation/native-stack
react-native-drawer-layout
react-native-tab-view	3.5.2
react-native-screens	3.29.0
react-native-safe-area-context	4.8.2
react-native-gesture-handler	2.25.0
react-native-reanimated	3.16.7
react-native-pager-view	6.2.3
react-native	0.74.4
expo
node
npm or yarn

Tried latest version of
@react-navigation/native 7.1.19
@react-navigation/bottom-tabs 7.8.4
@react-navigation/stack 7.6.3
same issue.

[github-actions]

Hey @ZaneRH! Thanks for opening the issue. It seems that the issue doesn't contain a link to a repro, or the provided repro is not valid (e.g. broken link, private repo, code doesn't run etc.).

The best way to get attention to your issue is to provide an easy way for a developer to reproduce the issue.

You can provide a repro using any of the following:

• Expo Snack
• TypeScript Playground
• GitHub repo under your username

A snack link is preferred since it's the easiest way to both create and share a repro. If it's not possible to create a repro using a snack, link to a GitHub repo under your username is a good alternative. Don't link to a branch or specific file etc. as it won't be detected.

Try to keep the repro as small as possible by narrowing down the minimal amount of code needed to reproduce the issue. Don't link to your entire project or a project containing code unrelated to the issue. See "How to create a Minimal, Reproducible Example" for more information.

You can edit your original issue to include a link to the repro, or leave it as a comment. The issue will be closed automatically after a while if you don't provide a valid repro.

[github-actions]

Couldn't find version numbers for the following packages in the issue:

• @react-navigation/native
• @react-navigation/stack
• @react-navigation/bottom-tabs
• @react-navigation/drawer
• @react-navigation/material-top-tabs
• react-native-drawer-layout
• react-native-tab-view

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

[github-actions]

Couldn't find version numbers for the following packages in the issue:

• @react-navigation/drawer
• @react-navigation/material-top-tabs
• react-native-drawer-layout

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

The versions mentioned in the issue for the following packages differ from the latest versions on npm:

• @react-navigation/native (found: 6.1.9, latest: 7.1.19)
• @react-navigation/bottom-tabs (found: 6.5.20, latest: 7.8.4)
• @react-navigation/stack (found: 6.3.20, latest: 7.6.3)
• react-native-tab-view (found: 3.5.2, latest: 4.2.0)

Can you verify that the issue still exists after upgrading to the latest versions of these packages?

[github-actions]

Couldn't find version numbers for the following packages in the issue:

• @react-navigation/drawer
• @react-navigation/material-top-tabs
• react-native-drawer-layout

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

The versions mentioned in the issue for the following packages differ from the latest versions on npm:

• react-native-tab-view (found: 3.5.2, latest: 4.2.0)

Can you verify that the issue still exists after upgrading to the latest versions of these packages?

[ZaneRH]

Just tried in iPad iOS26.1, pressing the default header will trigger the scrollable view on the screen scroll to top. And headerLeft button also trigger this.
In iOS18, pressing header will do nothing.
Previously only pressing the notification bar will trigger this...

[ienho]

This is a bug of the Apple system itself
The touch response area of the status bar extends far beyond the frame of the status bar itself，before Apple fixes the issue, you can use the following methods to avoid it

ScrollView.defaultProps = {
...ScrollView.defaultProps,
scrollsToTop: false
}

[ZaneRH]

This is a bug of the Apple system itself The touch response area of the status bar extends far beyond the frame of the status bar itself，before Apple fixes the issue, you can use the following methods to avoid it

ScrollView.defaultProps = { ...ScrollView.defaultProps, scrollsToTop: false }

Yes, no matter what views in that area, touch will always trigger scroll to top there

[github-actions]

Hello 👋, this issue has been open for more than a month without a repro or any activity. If the issue is still present in the latest version, please provide a repro or leave a comment within 7 days to keep it open, otherwise it will be closed automatically. If you found a solution or workaround for the issue, please comment here for others to find. If this issue is critical for you, please consider sending a pull request to fix it.

[matiastucci]

i'm also seeing this issue on a WebView component. Any ideas how to fix it? It doesn't support scrollsToTop prop.