/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 vote222 views1 answer
Plotly react
Javascript React
0 vote207 views1 answer
React return value from component
Javascript React
5 votes216 views1 answer
React dom
Javascript React
0 vote218 views1 answer
React native making bigger hitbox
Javascript React
0 vote247 views1 answer
Timezone in react js
Javascript React
23 votes265 views2 answers
Create-react-app npm yarn
Javascript React
0 vote223 views1 answer
React-native-ffmpeg gradel issue
Javascript React
0 vote203 views1 answer
Open modal on clicking select option in react
Javascript React
22 votes218 views3 answers
How to use if else inside jsx in react
Javascript React
3 votes202 views2 answers
React-native android build apk
Javascript React