Skip to content

/ rfcs

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

@brentvatne brentvatne commented Jul 18, 2018

@giacomocerquone
Copy link

@giacomocerquone giacomocerquone commented Aug 8, 2019

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 join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@brentvatne @giacomocerquone
You can’t perform that action at this time.