Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
NavigatorIOS crashes when "pushing" to a new route
See original GitHub issueError message:
Invariant Violation: No navigator item should be pushed without JS knowing about it 1 0"
The red screen is displayed as soon as a new route is pushed.
Sample app available at https://github.com/sharathprabhal/TestNavigatorIOS
Issue Analytics
- State:
- Created 8 years ago
- Reactions:1
- Comments:9 (4 by maintainers)
Top Results From Across the Web
React Native NavigatorIOS "PUSH" Crashes App When ...
The react-native application checks the local storage for an auth token, and if the token is available the app will navigate to the...
Read more >Stack Navigator
Pushes a new screen to top of the stack and navigate to it. The method accepts following arguments: name - string - Name...
Read more >Performance Overview
This often happens during Navigator transitions: when you push a new route, the JavaScript thread needs to render all of the components ......
Read more >[Solved]-Navigator vs NavigatorIOS React Native application
Coding example for the question Navigator vs NavigatorIOS React Native ... will be passed the route object you specified in navigator.push , which...
Read more >How to fix Maps when it crashes - Android
If the Google Maps app on your phone or tablet crashes or has other issues that affect your experience on Maps, try the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@brentvatne this still happens over a year later. It’d be great to be able to use a NavigatorIOS inside a NavigatorIOS. Having two different navigation stacks is a common pattern in iOS and is pretty much a must for our use case. The test repo provided by the OP is still relevant (https://github.com/sharathprabhal/TestNavigatorIOS)
I have just played around with this a bit and have a fix. Will post a pull request in a minute.
Can one use nested
Navigatorsall the way down, instead of usingNavigatorIOSin any level of that hierarchy?