/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 vote235 views2 answers
How to make a search bar in react django
Javascript React
4 votes230 views4 answers
React background gradient
Javascript React
2 votes242 views2 answers
Unable to resolve module react-navigation
Javascript React
0 vote231 views1 answer
Firebase integration in react
Javascript React
1 vote199 views1 answer
React native onpress show component
Javascript React
9 votes240 views5 answers
Find react version
Javascript React
1 vote192 views1 answer
Ctx in react
Javascript React
4 votes240 views1 answer
Reactjs onclick open new page
Javascript React
0 vote247 views1 answer
Horizontal scrollview in react js
Javascript React
0 vote275 views1 answer
How to change the choose file button text in react
Javascript React