/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

7 votes215 views4 answers
React router link
Javascript React
1 vote264 views1 answer
How to test useEffect in react testing library
Javascript React
0 vote193 views1 answer
Formatt json to create node and child node react
Javascript React
-2 votes210 views1 answer
How to get country code in react native
Javascript React
32 votes222 views1 answer
Install react router in react app
Javascript React
0 vote192 views1 answer
React return value from component
Javascript React
0 vote201 views1 answer
Bottom navigation bar react native hide on keyboard
Javascript React
2 votes198 views2 answers
Pdf table files download react not working
Javascript React
2 votes192 views2 answers
React native scrollview detect end
Javascript React
0 vote221 views1 answer
How to calc() height in react native for styling
Javascript React