Invariant Violation: requireNativeComponent: "RNSScreen" was not found in the UIManager #10575
-
|
I am getting RNSScreen error even though I have installed all related packages and followed react-navigation guide (https://reactnavigation.org/docs/getting-started#installation) but nothing worked for me. Your help is appreciated! Thanks! Note: I don't get this error when running on a simulator or running on an iPhone with the QR code. The error (and crash) only occurs in production mode.
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 6 replies
-
|
Delete .lock file and re install it. After that clear metro cache and start the application. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your reply! Delete the yarn.lock or package.lock or both? Sorry for the noob question, but how do I clear the metro cache? Thanks again! P.S. I just noticed that I left some important information out of my description. Sorry about that. I don't get this error when running on a simulator or running on an iPhone with the QR code. The error (and crash) only occurs in production mode. More supporting info: https://stackoverflow.com/questions/72104735/expo-with-drawer-navigator-crashes-on-ios-testflight-app-requirenativecomponen |
Beta Was this translation helpful? Give feedback.
-
|
Run cmd |
Beta Was this translation helpful? Give feedback.
-
|
Run |
Beta Was this translation helpful? Give feedback.
-
|
I updated Expo to 45.0.0. That fixed the error and solved a problem with the app crashing after launch in production mode but working fine on device with QR code or simulator. |
Beta Was this translation helpful? Give feedback.
-
|
As I told the packages were not compatible with SDK 44, upgrade solved the issue. |
Beta Was this translation helpful? Give feedback.
-
|
You’re correct that it was a package version issue, but you advised me to update expo to 44.0.0. I had to update expo to 45.0.0. I appreciate your help!
Larry
… On May 12, 2022, at 1:06 AM, Rajendran Nadar ***@***.***> wrote:
As I told the packages were not compatible with SDK 44, upgrade solved the issue.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
-
|
Yes that is great you upgraded to latest some people are still not read to upgrade to latest version so I gave you your current version so that there is no breaking changes and issue gets solved. |
Beta Was this translation helpful? Give feedback.
-
|
If people aren’t ready to upgrade to latest, how will they make a TestFlight build that doesn’t crash? I think there was a bug in Expo 44.0.0.
Larry
… On May 12, 2022, at 9:15 AM, Rajendran Nadar ***@***.***> wrote:
Yes that is great you upgraded to latest some people are still not read to upgrade to latest version so I gave you your current version so that there is no breaking changes and issue gets solved.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
-
|
I was using SDK 44 since 5 months never got a crash issue, you might have messed up some configuration, which got solved with |
Beta Was this translation helpful? Give feedback.
-
|
Could be. Thanks!
Larry
… On May 12, 2022, at 10:09 AM, Rajendran Nadar ***@***.***> wrote:
I was using SDK 44 since 5 months never got a crash issue, you might have messed up some configuration, which got solved with expo upgrade cmd
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
I updated Expo to 45.0.0. That fixed the error and solved a problem with the app crashing after launch in production mode but working fine on device with QR code or simulator.