Duplicate screen generated on navigation about cljs-react-navigation HOT 4 OPEN

@binora I am having a similar issue - which version of the lib are you using? Did you ever figure out what was causing this?

from cljs-react-navigation.

@andrew-nguyen i was using version 0.1.1. I couldnt solve it. This wasnt a bug in this library but react-navigation itself I think. This is a simliar issue : react-navigation/react-navigation#2904

from cljs-react-navigation.

@binora Thanks for the link. One thing I've noticed (using 0.1.3) is that the double-rendering only occurs in one of two situations for me:

1. After a figwheel reload (a button that was rendering only once prior to the reload is now double-rendering)
2. If I specify a stack of screens in a re-frame event and then navigate to that stack of screens

from cljs-react-navigation.

Not sure if this explains the behavior or if it's the correct fix but here's what I've done with my fork:

1. re-frame app-db stores clojure data structures (I did this primarily because I use the params feature to pass data to subsequent screens and ended up with a mix of clojure and js data structures within app-db. It seemed that always storing clojure structures and converting to js when necessary was the best path.)
2. cljs-react-navigation.re-frame functions have been changed to explicitly convert to js data structures (and back to clojure data structures when saving to app-db)
3. All of my downstream code now uses (dispatch-sync :cljs-react-navigation.re-frame/navigate ...) to navigate instead of the functions contained within the props

Everything generally appears to be working as expected.

@seantempesta If this makes sense, I'm happy to clean up my fork and submit a PR

from cljs-react-navigation.