/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 vote138 views1 answer
Flatpicker not focusing in modal React
Javascript React
0 vote96 views1 answer
Document is not defined react router
Javascript React
0 vote149 views1 answer
React native navigate two screens back
Javascript React
-1 vote144 views2 answers
Minified react error #200
Javascript React
0 vote152 views1 answer
Generate ios build react native
Javascript React
1 vote147 views2 answers
Push values to state array class react
Javascript React
11 votes159 views2 answers
React must be in scope when using jsx
Javascript React
0 vote103 views2 answers
Discord js remove all reactions from user
Javascript React
2 votes144 views2 answers
Pdf table files download react not working
Javascript React
-2 votes159 views2 answers
Search bar in react js material ui
Javascript React