/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 vote248 views1 answer
React native clear route params
Javascript React
0 vote278 views1 answer
Localhost server in react native
Javascript React
1 vote263 views1 answer
Three.js react
Javascript React
4 votes238 views2 answers
React materilize
Javascript React
0 vote261 views1 answer
11. Which of the following metals catch fire on reaction with air? A. Magnesium B. Manganese C. Potassium D. Calcium
Javascript React
1 vote273 views2 answers
Hosting react with pm2
Javascript React
0 vote246 views1 answer
Url in listitem react
Javascript React
0 vote240 views1 answer
React native hide stack navigator title
Javascript React
0 vote252 views2 answers
React useEffect prevent first time
Javascript React
21 votes262 views4 answers
React font awesome npm
Javascript React