/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

6 votes189 views1 answer
React-native italics
Javascript React
-2 votes172 views2 answers
Showdown react
Javascript React
-1 vote209 views5 answers
Play audio in react
Javascript React
0 vote181 views1 answer
React native firebase email verification
Javascript React
0 vote223 views1 answer
My env.local file not working in my react app usind mac
Javascript React
3 votes188 views2 answers
React is there a safe area view for android
Javascript React
18 votes256 views6 answers
Export apk react native
Javascript React
1 vote194 views1 answer
React native textinput no keyboard
Javascript React
15 votes234 views1 answer
Did you mean to use React.forwardRef()?
Javascript React
3 votes194 views2 answers
React how to scroll to element
Javascript React