Skip to content
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

Native Stack Navigator combining headerTransparent headerBlurEffect and headerShadowVisible does not work correctly on iOS #11618

Closed
3 of 12 tasks
jobpaardekooper opened this issue Sep 26, 2023 · 10 comments

Comments

@jobpaardekooper
Copy link

Current behavior

Using screenOptions for the stack navigator on iOS as follows:

{
    headerTransparent: true,
    headerBlurEffect: 'systemMaterial',
    headerShadowVisible: true,
}

Does not display the line on the bottom of the header on iOS.

Expected behavior

There should be a way to achieve the same header behavior as the iOS settings app where there is a blured background and gray line at the bottom. Here is a screenshot of the iOS settings header:

IMG_C7818C1133C4-1

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

Environment

  • I've removed the packages that I don't use
package version
@react-navigation/native 6.1.8
@react-navigation/native-stack 6.9.14
react-native-screens 3.25.0
react-native 0.72.5
node v16.13.0
npm or yarn 8.1.4
@github-actions
Copy link

Hey @jobpaardekooper! 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:

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
Copy link

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.

@github-actions github-actions bot added the stale label Oct 27, 2023
@jobpaardekooper
Copy link
Author

The issue still exists.

@github-actions github-actions bot removed the stale label Oct 28, 2023
@ljukas
Copy link

ljukas commented Nov 10, 2023

Can confirm still exists

Copy link

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.

@jobpaardekooper
Copy link
Author

Having a bot like this is not very productive...

I know it takes a bunch of time to go trough issues and I should really add a reproduction repo but, like the reviewers of these issues, I am also busy. This is not a super big critical issue so it is not such a big deal that it is not fixed but it is nice to have an issue that at least documents the problem is there.

Copy link

Hey! This issue is closed and isn't watched by the core team. You are welcome to discuss the issue with others in this thread, but if you think this issue is still valid and needs to be tracked, please open a new issue with a repro.

@smontlouis
Copy link

@jobpaardekooper having the same issue.
Did you manage to fix it ?

@jobpaardekooper
Copy link
Author

No I did not fix it.

@smontlouis
Copy link

smontlouis commented Jun 19, 2024

Found a workaround:

headerStyle: {
            backgroundColor:
                colorScheme === 'dark'
                  ? 'rgba(0,0,0,0.05)'
                  : 'rgba(255,255,255,0.05)'
          },

Instead of headerTransparent: true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants