/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

1 vote159 views2 answers
Toastandroid react native
Javascript React
0 vote134 views1 answer
How to resolve click for div logging as parent too, in react
Javascript React
4 votes122 views1 answer
React router history push parameter
Javascript React
0 vote180 views1 answer
React grid generator
Javascript React
3 votes120 views1 answer
React router dom current path hook
Javascript React
0 vote126 views1 answer
How to validate password and confirm password on react form hook
Javascript React
4 votes122 views1 answer
React native radio buttons
Javascript React
0 vote131 views1 answer
React bootstrap col not working
Javascript React
10 votes131 views1 answer
Dimensions react native
Javascript React
0 vote121 views1 answer
(0 , _reactRouterDom.useHistory) is not a function
Javascript React