/Javascript/React/React native getting old navigation parameter

React native getting old navigation parameter

The problem here is how navigation.navigate works. If you use it without
passing the key for the next screen, react-navigation won't match it with the 
screen that is already mounted hence mounting another one.

What you can observe here is exactly the case when the component was not yet 
unmounted but navigate doesn't know that and renders another instance of the 
same component.

You can prevent this by passing the key param into navigate function as follows:

navigation.navigate({name: 'ScreenB', key: 'ScreenB', params: { id: 1}})

navigation.navigate({name: 'ScreenB', key: 'ScreenB', params: { id: 2}})

Now StackNavigator can check if screen with the same key already exists and 
prevent it from mounting.

Similar codes

0 vote154 views1 answer
Casl react redux
Javascript React
32 votes319 views2 answers
How to routing in react js
Javascript React
0 vote151 views1 answer
React duration picker
Javascript React
0 vote154 views3 answers
React form validation
Javascript React
-2 votes147 views1 answer
React Pagination
Javascript React
18 votes134 views1 answer
Get specific characters from state variable reactjs
Javascript React
68 votes139 views4 answers
Inline styling react
Javascript React
0 vote173 views2 answers
React native use route params
Javascript React
1 vote97 views1 answer
Parent to child react state
Javascript React
0 vote169 views1 answer
Onclick react history map
Javascript React