/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 vote352 views1 answer
React native npm run start port
Javascript React
48 votes416 views6 answers
Comment in react
Javascript React
1 vote444 views1 answer
React native get mac address
Javascript React
0 vote418 views1 answer
Remove duplicate value from map react js
Javascript React
3 votes376 views2 answers
Autocomplete react jsx attributes vscode
Javascript React
7 votes414 views3 answers
React route props
Javascript React
0 vote422 views1 answer
How to trigger on Blur only when clicked outside parent component and not child component in react js
Javascript React
0 vote365 views1 answer
Making all makers to show in react native map
Javascript React
0 vote419 views1 answer
Localhost server in react native
Javascript React
0 vote382 views1 answer
Edit json text react
Javascript React