/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 vote181 views1 answer
Metro server not running react native
Javascript React
0 vote182 views1 answer
How to draw a long underline in react native
Javascript React
2 votes173 views1 answer
How to use `setState` callback on react hooks
Javascript React
0 vote183 views1 answer
Window.location.search get parameters react
Javascript React
0 vote175 views1 answer
React hook form example stack overflow
Javascript React
6 votes191 views2 answers
React in jquery
Javascript React
0 vote198 views1 answer
React prevent form submission on enter key press inside inputs
Javascript React
0 vote177 views1 answer
Node_modules/react-native-paper/lib/module/core/Provider.js
Javascript React
0 vote198 views1 answer
OnChange react functional programming
Javascript React
0 vote194 views1 answer
React check if mobile or desktop
Javascript React