-
-
Notifications
You must be signed in to change notification settings - Fork 537
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
App Crashes with message "-[RCTView setSheetLargestUndimmedDetent:]: unrecognized selector sent to instance" #2166
Comments
Hey! 👋 The issue doesn't seem to contain a minimal reproduction. Could you provide a snack or a link to a GitHub repository under your username that reproduces the problem? |
Hey! 👋 It looks like you've omitted a few important sections from the issue template. Please complete Description section. |
Setting |
Experiencing the same issue on iOS after updating React Native to 0.76. Running react-native-screens 3.35.0, and the latest 6.x.x versions of the required react navigation components. Using old architecture of RN. Crash happens immediately on opening the app. As @hoonjoo-park mentioned, adding |
@kkafar any chance someone could look into this? Seems to be some kind of incompatibility between screens and react-navigation. In our case, we are using the latest 6.x.x versions of "bottom-tabs", "native" and "stack" libraries of react-navigation, but without detachInactiveScreens disabled, the app crashes immediately on initialisation. Let me know if I can provide any further info to help debug this. |
The same error on my end, after installation. |
@spale44 screens 4.x are intended to work with |
@rodrigo-nexudus would you be able to provide me with a reproducible example where this happens? IMO this could only happen in case of version mismatch, since I can not reproduce this error in any other scenario. |
@kkafar @rodrigo-nexudus Tried with react-native-screens 3.35.0. I got the same error. Migrating React Native to 0.76.5 |
@kkafar our project is actually using 3.35.0 for react-native-screens, along with the following versions for the react-navigation libraries:
I did also, prior to your message, try to update to 4.4.0, but that did not resolve the issue. From playing around with it, it's affecting all the different navigators provided by react-navigation, as the 'detachInactiveScreens' prop needs to be applied to all navigators for the app not to crash. I can try and provide a minimal repo, but 3.35.0 was the initial setup where we experienced the issue. |
@rodrigo-nexudus it would be great if you had provided us with a repro - otherwise it's really hard to pin-point the issue |
@kkafar I am also getting same crash for ios. Is there any fix for this? |
@sriprasad19 I can reiterate on the need for reproduction. This looks like mismatch of versions as I've pointed above ☝ If anyone would be able to provide me with a proper reproduction / snack where I can reproduce the issue, then I might be able to fix the issue. |
Description
Problem
First of all, I've integrated ReactNative with my iOS native App.
There is no problem with using the basic components of ReactNative. However, when I register RootStackNavigator as an entryPoint, the app crashes with the following error:
-[RCTView setSheetLargestUndimmedDetent:]: unrecognized selector sent to instance
As I said above, my app is based on iOS, and only a few screens are implemented with ReactNative.
so I had to implement my custom BridgeManager which returns rootViewFactory to render ReactNative View.
React Native Code Example:
index.js
NoticeRootStackNavigator
iOS Code Example
CustomRCTBridgeManager.mm
NoticeViewController
Steps to reproduce
RCT_NEW_ARCH_ENABLED=1 bundle exec pod install
Snack or a link to a repository
sorry it's my company's private repo
Screens version
3.31.1
React Native version
0.74.2
Platforms
iOS
JavaScript runtime
Hermes
Workflow
React Native (without Expo)
Architecture
Fabric (New Architecture)
Build type
Debug mode
Device
iOS simulator
Device model
iPhone 15 Pro
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: