-
-
Notifications
You must be signed in to change notification settings - Fork 532
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
[iOS] RN v0.60 - Screen native module hasn't been linked. #125
Comments
Have you tried the following in Terminal?
|
I have the same problem with android |
perform the steps as mentioned in the other thread, but still throw the error that he comments. some way to fix it? |
Same problem here |
Works fine when switching off remote debugger. |
Same problem, rn version 0.59.9, any solutions? |
Run Update: @badgeek : See if disabling remote debugging works |
not working @herlarb |
I had the Same problem here with Android. Fresh project!
I then downgraded react-native-screens to 1.0.0-alpha.22 and did a |
I had the same problem with iOs. |
any solution about this for android with RN v.60? |
I am using a fresh project and I have this problem |
I had the same problem with iOs. |
I think this has been solved and i'm going to close the issue. Working fine for me running a fresh project with the latest release. |
in your podfile just add pod 'RNScreens', :path => '../node_modules/react-native-screens' then pod install it should work, I hate it but it seems not all RN Packages are autolinked |
@rafael-arreola did you find any solution so far? i am stuck on same issue |
I have the same problem with android, react-native 0.59.10 |
I have same problem in react-native 0.69.0 . it is occurring suddenly. what i missing? |
Created a fresh react native project and added react-navigation, react-native-gesture-handler & react-native-screens.
Added gesture handler and screens to the non auto linking config and did the appropriate
react-native link xxx
commands for both libraries. I then receive this error when loading the application:The text was updated successfully, but these errors were encountered: