/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 vote436 views1 answer
Setstate to false after 10 sec react native
Javascript React
2 votes397 views1 answer
Emmet react self closing tags
Javascript React
-1 vote397 views1 answer
React_Weather_App
Javascript React
0 vote344 views1 answer
React conditional if localhost
Javascript React
1 vote391 views1 answer
Change react native app name
Javascript React
0 vote514 views1 answer
Attempted import error: 'Map' is not exported from 'react-leaflet' (imported as 'LeafletMap').
Javascript React
0 vote388 views1 answer
S3 private image getobject react js
Javascript React
0 vote335 views1 answer
React native change image color
Javascript React
1 vote408 views3 answers
How to decode jwt token in react
Javascript React
125 votes529 views6 answers
Create React App command
Javascript React