/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 vote208 views1 answer
Active link color different in react js
Javascript React
0 vote234 views2 answers
How to use react typed js
Javascript React
0 vote243 views1 answer
React native sovrapporre immagini
Javascript React
6 votes224 views1 answer
React state management
Javascript React
0 vote255 views1 answer
Clickjacking in react js
Javascript React
0 vote222 views1 answer
Using RN BootSplash with React Navigation
Javascript React
1 vote221 views1 answer
Error: open failed: EACCES (Permission denied) react native
Javascript React
3 votes221 views2 answers
Get param is react
Javascript React
0 vote219 views2 answers
Loader in react
Javascript React
0 vote212 views1 answer
Form.Control textarea react bootstrap
Javascript React