-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Two routers, one for Main Application and one for Share application #2338
Comments
Well, it was working with an old version of RNRF, 3.38.0 It is not due to stateless components as I thought before, I have still the bug. |
@aksonov Any idea to help me, please ? |
It is not supported for v4, sorry. |
Questions, is it due to react-navigation or react-native-router-flux ? |
Version
Tell us which versions you are using:
Description
I have an application using RNRF with all routes. I created a share application, to be able to share photos with my main application on Android.
Old config in RNRF v3
I was creating two different routers for the main app and the share app. It was working fine.
I had to change routers component to be stateless to prevent warnings and doing so, my router component for the share part is not working anymore.
There is an error in getScreenForRouteName, line 21 saying `There is no route defined for key mainApplication. Must be one of 'shareApplicationRouteOne', 'shareApplicationRouteTwo'
Question
Do I have to do only one router component for the Main App and the Share App? Or is there something else I need to do ?
I made a fork reproducing the bug in Example folder here
https://github.com/arribbar/react-native-router-flux/tree/errorRouter
The text was updated successfully, but these errors were encountered: