/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

11 votes147 views4 answers
Prototype react
Javascript React
0 vote108 views1 answer
How to use algolia react native
Javascript React
2 votes154 views1 answer
React Refused to execute inline script because it violates the following Content Security Policy directive
Javascript React
10 votes157 views4 answers
React hooks
Javascript React
1 vote160 views2 answers
React state not updating immediately
Javascript React
16 votes152 views2 answers
Render text in for loop react in function
Javascript React
0 vote169 views1 answer
ResolveAssetSource react-native-web
Javascript React
0 vote137 views5 answers
React native cache clear
Javascript React
10 votes145 views2 answers
React text input onchange
Javascript React
0 vote159 views1 answer
React firebase add doc to collection
Javascript React