/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

21 votes272 views3 answers
Hide header bar react navigation
Javascript React
0 vote353 views1 answer
React native carriage return
Javascript React
1 vote340 views1 answer
Minimum flatlist size react native
Javascript React
0 vote348 views1 answer
React fontawesome exchange icon
Javascript React
0 vote385 views2 answers
Install boxicons in react
Javascript React
9 votes387 views1 answer
How to create a react app in current folder
Javascript React
1 vote369 views2 answers
React js alert popup example
Javascript React
0 vote331 views1 answer
Navigate to another page onPress button react native
Javascript React
0 vote355 views1 answer
React-native-quick-scroll npm
Javascript React
0 vote348 views1 answer
Open screen pdf on google drive react native expo
Javascript React