/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 vote118 views2 answers
React select disable option
Javascript React
4 votes127 views2 answers
Get request react
Javascript React
0 vote124 views1 answer
Prevent double tap in react native
Javascript React
0 vote123 views1 answer
Nested ternaries react
Javascript React
0 vote122 views1 answer
Js map vs react js map
Javascript React
0 vote139 views2 answers
Can i pass data with usenavigate react router
Javascript React
0 vote126 views1 answer
Set default types react
Javascript React
3 votes127 views1 answer
React native duplicate resources: Android
Javascript React
1 vote126 views1 answer
Have flat list automatically wrap react native
Javascript React
0 vote124 views1 answer
Could not resolve module fs react native
Javascript React