Skip to content
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

navigationsSate.children conflicts with another child #10

Closed
grigio opened this issue Apr 23, 2016 · 3 comments
Closed

navigationsSate.children conflicts with another child #10

grigio opened this issue Apr 23, 2016 · 3 comments

Comments

@grigio
Copy link

grigio commented Apr 23, 2016

Thanks for this Example, i noticed that if i tap on the buttons fast the app crashes

screenshot_20160423-194857

@athomasoriginal
Copy link

I ran into this issue as well. Make sure that your app is PUSHing and POPing...For me, the issue was that the app would never POP and this creates a duplicate key warning like you see above.

@jlyman
Copy link
Owner

jlyman commented Apr 25, 2016

Yep, there is certainly more guard logic that could be written into the pushing/popping actions. In a full application these state changes would likely be more complicated and involved; you'll want to make those decisions on a per-app basis.

@jlyman
Copy link
Owner

jlyman commented Aug 1, 2016

Closing due to age, feel free to re-open if need be.

@jlyman jlyman closed this as completed Aug 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants