/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 vote296 views1 answer
Switch react router
Javascript React
0 vote328 views1 answer
OnChange react functional programming
Javascript React
0 vote323 views1 answer
React native svg size
Javascript React
17 votes364 views5 answers
How to make apk react native
Javascript React
0 vote335 views1 answer
React input cursor jump end
Javascript React
1 vote344 views1 answer
React vscode stop auto close tag
Javascript React
6 votes329 views1 answer
React native rotate
Javascript React
0 vote302 views1 answer
Export all functions from js file react
Javascript React
6 votes331 views1 answer
React state management
Javascript React
2 votes338 views1 answer
React native seperator code
Javascript React