/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 vote309 views1 answer
React build size
Javascript React
0 vote302 views1 answer
React native Setting a timer for a long period of time
Javascript React
0 vote286 views1 answer
Inline style to change background color react
Javascript React
1 vote312 views1 answer
React admin newrecords.foreach is not a function
Javascript React
13 votes299 views1 answer
React post request
Javascript React
1 vote275 views1 answer
Bootstrap icons react
Javascript React
0 vote352 views1 answer
Convert integer month to string month react native
Javascript React
140 votes452 views5 answers
React js installation
Javascript React
9 votes307 views6 answers
React Component
Javascript React
0 vote301 views1 answer
Installation de react native maps bibliothèque
Javascript React