/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

1 vote176 views1 answer
Class and id in react
Javascript React
0 vote184 views1 answer
React native jest snapshot
Javascript React
13 votes256 views3 answers
React native conditional rendering
Javascript React
0 vote147 views1 answer
React testing library getBy image
Javascript React
85 votes210 views6 answers
Redirect react router
Javascript React
0 vote371 views1 answer
React native multiple touchableopacity
Javascript React
0 vote177 views1 answer
Cannot find module react scripts
Javascript React
0 vote197 views1 answer
React video srcObject
Javascript React
112 votes249 views10 answers
React
Javascript React
0 vote190 views1 answer
Duplicate module name: React Native hasteimpl react native android
Javascript React