Samuel
should probably file a bug report with react-navigation but cba to jump through all the hoops rn, maybe later
1 4
Samuel
yeah probably true. @danabra.mov I've generalised the bug to be 1. go to a page (e.g. /one) 2. go to another page 3. use browser back button 4. go to a page (doesn't need to be the same as step 2) 5. go to /one browser history and react-navigation history get out of sync, history.go overshoots
1 4
Samuel
@samuel.fm
wait sorry my steps are wrong 1. go to an initial page (e.g. /one) 2. navigate to /two 3. navigate to /three 4. use back button 5. navigate to /four 6. navigate to /one
4