Package
@effector/router-react-native
What happened?
Bottom Tabs derives screen names by removing slashes from route paths. For example, the route path /home becomes the screen name home. However, initialRouteName is passed through unchanged, and the documentation uses /home.
React Navigation therefore receives an initial route name that does not exist in the generated screen list.
Reproduction
- Create a route with path /home.
- Pass its RouteView to createBottomTabsNavigator.
- Set initialRouteName: '/home'.
- Observe that the configured initial screen name does not match the registered tab name home.
Expected: initialRouteName uses the same name that the navigator generates, or route names are preserved consistently.
Actual: the docs and configuration use /home while the generated screen is named home.
Environment
- @effector/router-react-native: 1.0.1
- @effector/router: 1.1.1
- React: 18 or 19
- React Native: >=0.70
- React Navigation Bottom Tabs: >=6
- Node.js: 24.x
Logs / screenshots
Not applicable; the mismatch is deterministic.
Package
@effector/router-react-native
What happened?
Bottom Tabs derives screen names by removing slashes from route paths. For example, the route path /home becomes the screen name home. However, initialRouteName is passed through unchanged, and the documentation uses /home.
React Navigation therefore receives an initial route name that does not exist in the generated screen list.
Reproduction
Expected: initialRouteName uses the same name that the navigator generates, or route names are preserved consistently.
Actual: the docs and configuration use /home while the generated screen is named home.
Environment
Logs / screenshots
Not applicable; the mismatch is deterministic.