Safe Area Ignored in React Native 0.77, New Architecture Enabled

[anultravioletaurora]

Current behavior

On react-native:0.77, with the New Architecture enabled, my bottom tabs and native stack navigators are ignoring the safe area. I have a SafeAreaProvider at the top of my app, with my NavigationContainer nested in it as follows:

  return (
    <SafeAreaProvider>
      <NavigationContainer theme={isDarkMode ? JellifyDarkTheme : JellifyLightTheme}>
        { loggedIn ? (
          <PlayerProvider>
            <Navigation />
          </PlayerProvider>
         ) : (
           <JellyfinAuthenticationProvider>
            <Login /> 
          </JellyfinAuthenticationProvider>
        )}
        <SafeToastViewport />
      </NavigationContainer>
    </SafeAreaProvider>
  )

Expected behavior

Safe Areas respected and avoided

Reproduction

https://github.com/anultravioletaurora/Jellify/tree/64-support-react-natives-new-architecture

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-drawer-layout
• react-native-tab-view

Environment

• I've removed the packages that I don't use

package	version
@react-navigation/native	^7.0.14
@react-navigation/bottom-tabs	^7.2.0
@react-navigation/drawer	N/A
@react-navigation/material-top-tabs	N/A
@react-navigation/stack	^7.1.1
@react-navigation/native-stack	^7.2.0
react-native-drawer-layout	N/A
react-native-tab-view	N/A
react-native-screens	^4.8.0
react-native-safe-area-context	^5.2.0
react-native-gesture-handler	^2.24.0
react-native-reanimated	^4.0.0-beta.2
react-native-pager-view	N/A
react-native	0.77.0
expo	^52.0.37
node	20
npm or yarn	npm

[github-actions]

Hey @anultravioletaurora! Thanks for opening the issue. It seems that the issue doesn't contain a link to a repro, or the provided repro is not valid (e.g. broken link, private repo, code doesn't run etc.).

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

[github-actions]

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

• @react-navigation/drawer
• @react-navigation/material-top-tabs
• react-native-drawer-layout
• react-native-tab-view

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

[anultravioletaurora]

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

• @react-navigation/drawer
• @react-navigation/material-top-tabs
• react-native-drawer-layout
• react-native-tab-view

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

Not using them 👍

[EHF32]

Same issue, any workaround?

[GonzaArts]

I have the same problem

[anultravioletaurora]

This issue still persists with 'react-native': '0.78.0' and 'react-native-screens': '4.9.0'

I'm not sure if this is directly caused by react-native-safe-area-context or not, as they state their support for the new architecture is experimental

[AZagatti]

Hey, if you're using headerShown: false, you now need to handle this properly. Please follow this guide: https://reactnavigation.org/docs/handling-safe-area

[anultravioletaurora]

Hey, if you're using headerShown: false, you now need to handle this properly. Please follow this guide: https://reactnavigation.org/docs/handling-safe-area

I'm not using headerShown: false 🙁 I have a native stack that is rendering a header. I also am not sure as to why my tab bar isn't positioned correctly 🤔

[Prashants23]

I am facing this issue on RN 0.76.7 as well. Is there any workaround for this?

[anultravioletaurora]

I am facing this issue on RN 0.76.7 as well. Is there any workaround for this?

I don't have anything yet, I've upgraded to the latest versions of each of the packages mentioned in the original post, and I'm still running into the same issue

I'm not sure if this is the cause? appandflow/react-native-safe-area-context#586 (comment)