Open vonovak opened 8 years ago
I am seeing the same behavior, as I set the debugger in chrome to pause on exceptions...which is not usable with this behavior. is there a formality/standard we are missing in implementing the navigator that would resolve this exception? @vonovak
This error message shows up in chrome when debugging, but it actually doesn't have any noticeable effect, ie. the navigation works. Maybe it happens when a navigator is a root navigator (has no parent)?