Header height not getting calculated in pageY value for components in new architecture about react-native HOT 6 OPEN

Hi @ManiTWIndia, we will be releasing a new version of react-native-screens today (or tomorrow), so I believe beta won't be needed for now! 😄
The release will include fixes with incorrect target of touchables, so this issue should be resolved after updating screens to 3.30.0 version (or higher ones).

from react-native.

Do you know if we somehow need to bump screens version to make this issue fixed? I know that screens are defined as a peer dependency in stack, but maybe defining it also as the dev dependency impacts that "contract"?

Nope, only the version installed and linked into the project can impact it.

from react-native.

@ManiTWIndia Thanks for reporting this.
I believe the issue here is that you're using react-native-screens under the hood which is affected by this bug:
#36710

Can you try again on 0.74 + do a patch-package of react-native-screens

software-mansion/react-native-screens#2028

and report back if the issue is fixed?

from react-native.

Hi @cortinico I am facing some issues in using patch-package of react-native-screens. There are lot of commits after the last release version. Can we get a beta release of react-native-screens to test it out in local?
Thanks

from react-native.

@tboba @cortinico With and without header, its still showing the same pY value. I have updated and using the latest packages in the project. I have pushed the changes. Can you please check in the repo to reverify the issue?
Thanks

FYI, I am running the project with RN 0.73.6
When running with RN 0.74, facing below issue when running ios

CompileC /Users/manikanda.s/Library/Developer/Xcode/DerivedData/popoverIssueNew-cmchexkcvzazmngmguhjojjurspp/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/react-native-safe-area-context.build/Objects-normal/arm64/RNCSafeAreaViewShadowNode.o /Users/manikanda.s/Desktop/TWMarch/popoverIssueNew/node_modules/react-native-safe-area-context/common/cpp/react/renderer/components/safeareacontext/RNCSafeAreaViewShadowNode.cpp normal arm64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'react-native-safe-area-context' from project 'Pods')

from react-native.

@ManiTWIndia Yeah, I can reproduce that on your example. However, after changing the navigator from stack to native-stack, the button has correct target!

I'm curious why this bug still occurs on JS stack, maybe because it still uses ~3.20.0 as the dev dependency of stack?
cc @satya164 Do you know if we somehow need to bump screens version to make this issue fixed? I know that screens are defined as a peer dependency in stack, but maybe defining it also as the dev dependency impacts that "contract"?

from react-native.