Unexpected behavior: headerShadow unexpectedly visible

Softkeydel commented 1 month ago

Current behavior

Header shadow visible unexpectedly

https://github.com/user-attachments/assets/2edb6e0e-3520-4b80-b765-6db9b961456b

Already tried with most updated versions of the libraries mentioned

Expected behavior

Header shadow should not visible

https://github.com/user-attachments/assets/bd561646-a000-498b-bc31-9c86a9ba257c

Reproduction

https://github.com/Softkeydel/Reproduce

Platform

[X] Android
[ ] iOS
[ ] Web
[ ] Windows
[ ] MacOS

Packages

[ ] @react-navigation/bottom-tabs
[X] @react-navigation/drawer
[ ] @react-navigation/material-top-tabs
[ ] @react-navigation/stack
[X] @react-navigation/native-stack
[ ] react-native-tab-view

Environment

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

package	version
@react-navigation/native	6.1.17
@react-navigation/drawer	6.7.0
@react-navigation/native-stack	6.10.0
react-native-safe-area-context	4.10.8
react-native-screens	3.32.0
react-native-gesture-handler	2.16.2
react-native-reanimated	3.10.1
react-native	0.72.15
react	18.2.0
node	20.15.1
npm	10.7.0

github-actions[bot] commented 1 month ago

Hey @Softkeydel! 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.

Softkeydel commented 1 month ago

GitHub repo added pls check

Nonag commented 1 month ago

I have the same issue on a screen with a transparent header.

When first adding the screen to the stack, the header is presented as expected. But as soon as you add another screen on top and then navigate back to the screen with the transparent header, the shadow was added.

Softkeydel commented 1 month ago

@Nonag any solution??

edritech93 commented 1 month ago

same issue for me, any solution ?

ngondat97 commented 1 month ago

same issue

santiagomariani-tiendanube commented 1 month ago

same issue

wangchongwei commented 1 month ago

same issue

sakarzac000 commented 3 weeks ago

Same as well. It's worth noting that I wasn't having this issue before using Fabric, but switching to the new arch made it show up.

github-actions[bot] commented 3 weeks ago

Hey! Thanks for opening the issue. Seems that this issue is related to react-native-screens library which is a dependency of React Navigation. Can you also post your issue in this repo so that it's notified to the maintainers of that library? This will help us fix the issue faster since it's upto the maintainers of that library to investigate it.