Skip to content
This repository has been archived by the owner on Aug 8, 2024. It is now read-only.

More robust way to handle top-level navigator differences #56

Open
brentvatne opened this issue Jul 18, 2018 · 1 comment
Open

More robust way to handle top-level navigator differences #56

brentvatne opened this issue Jul 18, 2018 · 1 comment

Comments

@brentvatne
Copy link
Member

@giacomocerquone
Copy link

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brentvatne @giacomocerquone