-
Notifications
You must be signed in to change notification settings - Fork 134
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
AppRegistry.setWrapperComponentProvider not called : nothing rendered #44
Comments
Use break point to see why it's not called |
Ok so, after diving into react-native source code, i understood that AppRegistry.setWrapperComponentProvider is called twice, both with RootSiblingsWrapper but used by different modules :
I think the problem comes from here, everything is being called, AppContainer render
[EDIT] |
The latest version of react-native-root-siblings has a flag to check whether it is invoked twice. You and all your third parties should use the latest version. (Just delete node_modules and lock files and then reinstall may work) |
See #43 |
Hello,
i experience for 2 days now some weird behavior (nothing happens), it was working perfectly before.
i've tracked the issue :
AppRegistry.setWrapperComponentProvider
is not called at all.const triggers = []
remains empty and nothing renderI dont think the issue is with react-native-root-sibling, as i said it was working before and i already had the last version.
I think it's deep in react or some side module having a side effect.
Would you have any idea what could cause that ?
"react-native": "0.57.8"
(i can't upgrade this)the only module changes i made was to reinstall lottie (it was already installed before though), tried to remove it and see what it does but nothing changes.
The text was updated successfully, but these errors were encountered: