More robust way to handle top-level navigator differences
brentvatne opened this issue · 1 comments
brentvatne commented
giacomocerquone commented
A bit of more context here? As stated in this my other comment (react-navigation/react-navigation#4490 (comment)), I'd like to know why this happens.
Exactly why the reference is set after the navigator (and its screens) are rendered