/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

1 vote349 views2 answers
Use state reactjs
Javascript React
0 vote331 views4 answers
How to pass data between routes in react
Javascript React
0 vote233 views2 answers
React refresh page not found
Javascript React
0 vote370 views1 answer
Icon with label in react native
Javascript React
18 votes308 views6 answers
Import svg react
Javascript React
4 votes298 views1 answer
React js materilize
Javascript React
0 vote346 views2 answers
Go back to screen with params react native
Javascript React
0 vote333 views1 answer
React js date ago
Javascript React
0 vote325 views1 answer
React-native-checkbox in a loop
Javascript React
0 vote286 views1 answer
Créer composant react
Javascript React