/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 vote294 views1 answer
Import pdfmake in react
Javascript React
4 votes336 views2 answers
Onitemclick react
Javascript React
0 vote324 views1 answer
Nested arrays reactjs tables
Javascript React
0 vote349 views1 answer
Align image center react native
Javascript React
0 vote376 views2 answers
Datepicker range npm reactjs
Javascript React
0 vote324 views1 answer
Usb react native device not found
Javascript React
0 vote327 views1 answer
Only numbers or string. Input field in React
Javascript React
0 vote354 views3 answers
React native shaddow
Javascript React
0 vote319 views1 answer
React select remove the loading indicator
Javascript React
2 votes340 views1 answer
Display image as big as possible react native
Javascript React