Incorrect pageY value when only using default header of react navigation stack in new architecture

[ManiTWIndia]

          In old architecture and in new architecture android, the pageY value is returned as expected. Even in iOS, when i use headerShown: false or custom header in react-navigation stack, the pageY value is returned as expected.

I am seeing this issue only when using the default header of react-navigation stack in new architecture. So please do have a look

Originally posted by @ManiTWIndia in #11894 (comment)

Reproduction

https://github.com/ManiTWIndia/stack-navigation-header-issue

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-tab-view

Environment

package	version
@react-navigation/native	6.1.16
@react-navigation/stack	6.3.28
react-native-safe-area-context	4.9.0
react-native-screens	3.29.0
react-native-gesture-handler	2.15.0
react-native-reanimated	3.8.0
react-native	6.1.16
node	v20.11.1
npm or yarn	10.2.4

[github-actions]

Hey @ManiTWIndia! Thanks for opening the issue. It seems that the issue doesn't contain a link to a repro.

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 repro.

[github-actions]

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

• @react-navigation/native

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

[satya164]

How do you expect React Navigation to fix what pageY you get when none of those APIs are implemented by React Navigation?

Please don't open the same issue multiple times.