/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 vote417 views3 answers
Github react hardhat nft marketplace application
Javascript React
0 vote225 views1 answer
Toggle boolean state react
Javascript React
0 vote329 views1 answer
When reload the page the route gone in react js laravel
Javascript React
0 vote334 views1 answer
React router nested routes active
Javascript React
0 vote230 views1 answer
How to insalk react router with npm
Javascript React
0 vote244 views1 answer
Toggle class onscroll hook react
Javascript React
0 vote204 views1 answer
Detect the city on application launch via geolocation react native
Javascript React
0 vote211 views1 answer
React faq
Javascript React
0 vote259 views1 answer
React-leaflet/core/cjs/pane.js:7%20error15-Jun-2021%2000:45:06%20%20%20%20%20%20const%20pane%20=%20props.pane%20??%20context.pane;
Javascript React
63 votes226 views6 answers
React router install
Javascript React