/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 vote245 views1 answer
React native navigation paramlist never used
Javascript React
0 vote256 views1 answer
_40 0 _55 null _65 0 _72 null react native fetch
Javascript React
1 vote250 views1 answer
React material ui classname
Javascript React
24 votes220 views3 answers
Set port in react app
Javascript React
0 vote239 views1 answer
Publish reactjs package to gitlab repository
Javascript React
2 votes233 views1 answer
React native open email client expo
Javascript React
6 votes295 views1 answer
How to import dotenv in react
Javascript React
24 votes370 views3 answers
Reactjs sass setup
Javascript React
0 vote246 views1 answer
Provider not found react
Javascript React
1 vote237 views2 answers
Can't perform a react state update
Javascript React