Invariant Violation: requireNativeComponent: "RNSModalScreen" was not found in the UIManager.

[ayushthumar]

Current behavior

Below is my code and I am not using expo, I am using the react-native cli:

import * as React from 'react';
import { Text, View } from 'react-native';
import { NavigationContainer } from '@react-navigation/native';
import { createBottomTabNavigator } from '@react-navigation/bottom-tabs';

function HomeScreen() {
  return (
    <View style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}>
      <Text>Home!</Text>
    </View>
  );
}

function SettingsScreen() {
  return (
    <View style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}>
      <Text>Settings!</Text>
    </View>
  );
}

const Tab = createBottomTabNavigator();

export default function App() {
  return (
    <NavigationContainer>
      <Tab.Navigator>
        <Tab.Screen name="Home" component={HomeScreen} />
        <Tab.Screen name="Settings" component={SettingsScreen} />
      </Tab.Navigator>
    </NavigationContainer>
  );
}

This is the error I am getting

Invariant Violation: requireNativeComponent: "RNSModalScreen" was not found in the UIManager.

This error is located at: in RNSModalScreen in Unknown (created by InnerScreen) in Suspender (created by Freeze) in Suspense (created by Freeze) in Freeze (created by DelayedFreeze) in DelayedFreeze (created by InnerScreen) in InnerScreen (created by Screen) in Screen (created by MaybeScreen) in MaybeScreen (created by BottomTabView) in RNSScreenNavigationContainer (created by ScreenContainer) in ScreenContainer (created by MaybeScreenContainer) in MaybeScreenContainer (created by BottomTabView) in RNCSafeAreaProvider (created by SafeAreaProvider) in SafeAreaProvider (created by SafeAreaProviderCompat) in SafeAreaProviderCompat (created by BottomTabView) in BottomTabView (created by BottomTabNavigator) in PreventRemoveProvider (created by NavigationContent) in NavigationContent in Unknown (created by BottomTabNavigator) in BottomTabNavigator (created by App) in EnsureSingleNavigator in BaseNavigationContainer in ThemeProvider in NavigationContainerInner (created by App) in App in RCTView (created by View) in View (created by AppContainer) in RCTView (created by View) in View (created by AppContainer) in AppContainer in appUI(RootComponent), js engine: hermes

Screenshot

Expected behavior

What I want is

Reproduction

https://reactnavigation.org/docs/tab-based-navigation

Platform

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

Packages

• [X] @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.17
@react-navigation/bottom-tabs	6.5.20
react-native	0.73.6
node	18.0.0
npm or yarn	10.5.0

[github-actions[bot]]

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

[github-actions[bot]]

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

• @react-navigation/native
• @react-navigation/bottom-tabs
• @react-navigation/drawer
• @react-navigation/material-top-tabs
• @react-navigation/stack
• 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.

[Dhruv-88]

hello @ayushthumar can you share how you resolve this issue please ?

[github-actions[bot]]

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.

[ayushthumar]

hello @ayushthumar can you share how you resolve this issue please ?

Hello @Dhruv-88, I just deleted the build file in ios folder and then rebuild it, and also I stopped the server at port 8081 and restarted it ! Let me know if it works for you or not !

[WyattBensman]

I am using Expo, and I am receiving the same error with the same code you provided. Any insight on how to correct this? I saw you mentioned deleting the build file in the ios folder, where exactly is this? Any other tips?

[ayushthumar]

I am using Expo, and I am receiving the same error with the same code you provided. Any insight on how to correct this? I saw you mentioned deleting the build file in the ios folder, where exactly is this? Any other tips?

In your home directory there will be ios folder, go in that folder and run command rm -r build and then again run the app in simulator or your device that will automatically create new latest build file.

[ayushthumar]

I did not found any other valid and sensible solution for this issue, I am assuming that this issue came with the new version. @brentvatne @skevy @satya164 can you please help us on this.

[netshade]

I think you may have accidentally tagged me on this issue, I'm not able to assist with this.

[WyattBensman]

I am using Expo, and I am receiving the same error with the same code you provided. Any insight on how to correct this? I saw you mentioned deleting the build file in the ios folder, where exactly is this? Any other tips?

In your home directory there will be ios folder, go in that folder and run command rm -r build and then again run the app in simulator or your device that will automatically create new latest build file.

I sadly don't have the same file structure. I will continue to trouble shoot & hopefully find a solution.

[aminesebastian]

Just want to report I'm experiencing this too on Expo. I was able to resolve it by downgrading react-native-screens to 3.29.0:

npm install react-native-screens@~3.29.0

[jeremiasr]

Thanks! aminesebastian it's work!

[gulsher7]

same error facing . Tried all methods but now working

[Petercopter]

Same error as OP here. Another similarity is that it's the Tabs component

• Using Expo with file based routing
• Navigating from sign in (root) to /(app)/(tabs)
• Downgrading from 3.30.1 to 3.29.0 resolves the issue

[Generalchrist]

I'm encountering the same issue as described in this thread. However, I'm using createStackNavigator as outlined in the documentation.

While the application runs smoothly on the Android emulator, it throws the following error and gets stuck at the splash screen when launched on my iPhone 7:

ERROR Invariant Violation: requireNativeComponent: "RNSModalScreen" was not found in the UIManager.

• I'm not using react-native-screens
• I'm using expo so I don't have the same folder structure

EDIT: I solved it by this command: npx expo install react-native-screens react-native-safe-area-context I don't use these packages but somehow something needs them.

[abisalde]

Just want to report I'm experiencing this too on Expo. I was able to resolve it by downgrading react-native-screens to 3.29.0:

npm install react-native-screens@~3.29.0

This works

[protonforest]

yeah theres definetly something wrong with the last 3.30 version

[codegabk]

Is there a workaround without downgrading from 3.30 to 3.29 ?

[ayushthumar]

Is there a workaround without downgrading from 3.30 to 3.29 ?

Till now I have not found any other way to get the work done with 3.30 !