/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

11 votes104 views5 answers
React router refresh page
Javascript React
32 votes275 views2 answers
How to routing in react js
Javascript React
1 vote139 views1 answer
How to find the width of outerconatiner in react native
Javascript React
1 vote96 views1 answer
When i go srource in react app in chrome i see my files
Javascript React
1 vote100 views1 answer
Axios upload progress react
Javascript React
0 vote107 views1 answer
Detecting change in animated value react native
Javascript React
40 votes107 views5 answers
Fetch react
Javascript React
0 vote122 views1 answer
Start live server react js
Javascript React
1 vote118 views1 answer
Reactjs cloudflare
Javascript React
-1 vote103 views3 answers
Divider in react native
Javascript React