-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
Class RCTCxxModule was not exported. Did you forget to use RCT_EXPORT_MODULE()? #18201
Comments
I'm having the same issue after I upgraded to RN 0.54. |
I have this issue too after upgrading to RN 0.54.1. If I reload the app in the simulator the warning goes away. |
Same as @leejones45, getting this error after upgrading and only on first load. |
Same with me |
Same with me |
Same here when running on my device via xCode. |
Same here with |
Also seeing this with |
This is a duplicate of #14806 It's a harmless issue and you can ignore it, but quite confusing when you encounter it at first. Sadly it seems that nobody had the time to fix this yet, so it is still in the current version. |
Me too in RN@0.55 |
me too |
3 similar comments
me too |
me too |
me too |
me too and a bunch of issues with Yoga include< algorithm > etc. |
Any update on this issue? I know it's harmless but it still bothers me |
The message should be removed if it's really not an issue. Or FB needs to fix the condition that checks for whatever it is this is trying to check for. |
Any update on this? When I want to run on device, I need to have RCTNetwork.xcodeproj and RCTWebSocket.xcodeproj manually linked but when I archive my app I have to delete both and add this code to my pod file and run pod install :
Otherwise I have errors. I also upgrade react-native to 55.3 from 51. |
I've also found that when archiving, the Regular debug & release builds need the |
me too in RN@0.54 |
Thanks for posting this! It looks like your issue may refer to an older version of React Native. Can you reproduce the issue on the latest release, v0.55? Thank you for your contributions. |
Dear Mr bot, This occurs with RN 0.55.3 and probably any newer version. |
same with me in react-native@0.55.4 |
So what is the solution then ? |
@frayhan32 For now it's not the best solution, but to avoid the warning we can ignore it:
|
I haven't proven my theory but I just started getting this (and another warning: "RCTImageLoader requires main queue setup...") and the only change I made was to use YellowBox (as per prev comment) instead of the old |
@charlot567 Note that same method is used to prevent the "isMounted(...) is deprecated" yellow box appear in |
This is a duplicate of #14806 so I'll close and lock this to avoid spam/useless comments |
There are warnings on app start:
Environment
Expected Behavior
No warnings.
Actual Behavior
There are warnings.
Steps to Reproduce
react-native init AwesomeProject
ios/AwesomeProject.xcodeproj
I've tested several versions back (0.49) and the issue is there as well.
Sample project
https://github.com/vshab/react-native-0.54-run-warning
The text was updated successfully, but these errors were encountered: