/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 vote303 views1 answer
React time input
Javascript React
0 vote300 views1 answer
Reactjs exemple class component
Javascript React
4 votes296 views2 answers
Onitemclick react
Javascript React
6 votes286 views2 answers
TextInput disable react native
Javascript React
9 votes244 views4 answers
Firebase' is not defined no-undef react
Javascript React
10 votes357 views2 answers
Generate random string react
Javascript React
0 vote311 views1 answer
How to reset count in react
Javascript React
0 vote274 views1 answer
Ts(2749) react testing library
Javascript React
0 vote303 views2 answers
How to hide api key in react
Javascript React
1 vote289 views1 answer
Stream closed react native
Javascript React