/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 vote286 views1 answer
How to declare a variable in react
Javascript React
1 vote165 views1 answer
React 360
Javascript React
7 votes179 views2 answers
Input type password react native
Javascript React
0 vote182 views1 answer
Burger menu bulma React
Javascript React
0 vote213 views1 answer
Htaccess to deploy react app to cpanel
Javascript React
0 vote205 views1 answer
React electron desktop app
Javascript React
0 vote196 views1 answer
React document documentMode not found
Javascript React
0 vote227 views1 answer
Login condition if and else in router dom of react jsx
Javascript React
0 vote296 views2 answers
React native use route params
Javascript React
3 votes188 views2 answers
Handle onchange react
Javascript React