/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

17 votes275 views3 answers
React canvas clear
Javascript React
0 vote231 views2 answers
Dispay react component after some time
Javascript React
0 vote275 views1 answer
Reactnaviataion change title
Javascript React
0 vote264 views1 answer
Make 2div in row react js
Javascript React
0 vote276 views1 answer
Style react native alert text
Javascript React
15 votes265 views2 answers
UseReducer() hook react
Javascript React
0 vote244 views1 answer
Add update react pwa feature
Javascript React
0 vote282 views1 answer
Difference between controlled and uncontrolled components in react js
Javascript React
0 vote266 views1 answer
How to run and clone react app
Javascript React
5 votes269 views4 answers
Export default react
Javascript React