/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 vote363 views1 answer
React native svg onpress
Javascript React
50 votes314 views6 answers
Yarn create react app
Javascript React
4 votes377 views1 answer
Text input placeholder color react native
Javascript React
0 vote314 views1 answer
Integrate my own google pay using react js
Javascript React
34 votes328 views3 answers
React-router
Javascript React
2 votes370 views2 answers
Horizontal divider react native
Javascript React
0 vote347 views2 answers
Animation react
Javascript React
0 vote344 views1 answer
How to use mdbreact in react js
Javascript React
2 votes387 views4 answers
Date range picker react
Javascript React
0 vote355 views1 answer
React computed example
Javascript React