/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 vote124 views1 answer
React open a link to an outside siite
Javascript React
0 vote138 views1 answer
Uuid for react native
Javascript React
0 vote171 views1 answer
React native run on specific emulator
Javascript React
0 vote131 views1 answer
React features
Javascript React
0 vote134 views1 answer
How to write sepearet styles in single line in react native
Javascript React
6 votes143 views2 answers
React native spinkit
Javascript React
0 vote138 views1 answer
Eslint init settings for ReactJS
Javascript React
9 votes143 views2 answers
Android center text react native
Javascript React
0 vote141 views2 answers
React firebase hooks
Javascript React
0 vote137 views1 answer
React.common.JavascriptException: Error: invalid host
Javascript React