-
-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
containedModal presentation with transparent header has useHeaderHeight value of 0 on iOS #10333
Comments
Couldn't find version numbers for the following packages in the issue:
Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3. |
All good. not used. |
I'm having this issue too, though I am seeing the problem for presentation |
I'm having a similar issue.
When showing a Screen inside a native StackNavigator using
Whats interesting, when calling
|
This issue is still there in 6.6.2. As @klandell said, when I downgrade my |
Is there any workaround for this? I've resorted to hardcoding a value if the |
Current behavior
Recent changes to
native-stack
and how the transparent headers work has caused one scenario to have issues still (the other scenarios were recently fixed):On iOS, a modal screen presented as a
'containedModal'
presentation type that has a transparent header has a header height of 0 returned fromuseHeaderHeight
. On Android, it's returning the correct height.The correct height height was being returned in native-stack version 6.2.5. Then in 6.3.0 it became 0.
The issue was corrected for all but this one scenario in 6.4.1. The issue still happens in 6.4.1/6.5.0 (latest) for this specific presentation mode.
6.2.5 iOS ✅:
6.5.0 iOS ❌:
6.5.0 Android ✅:
Snack provided shows the issue.
Expected behavior
A non-zero header height should be returned for iOS when a transparent header is presented as
containedModal
.Reproduction
https://snack.expo.dev/@jstheoriginal/containedmodal-transparent-header-height-0
Platform
Packages
Environment
The text was updated successfully, but these errors were encountered: