/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 vote108 views1 answer
Cannot find module '@babel/runtime-corejs2/helpers/interoprequiredefault' in react native
Javascript React
0 vote118 views1 answer
Insert isValidPhoneNumber in react hook form
Javascript React
0 vote114 views1 answer
Reactnaviataion change title
Javascript React
0 vote144 views1 answer
Style react native alert text
Javascript React
0 vote117 views2 answers
React native view background transparency
Javascript React
0 vote118 views1 answer
Library to add navigation in react native
Javascript React
11 votes112 views3 answers
Shadow border react native
Javascript React
2 votes106 views1 answer
React refresh page every second
Javascript React
0 vote104 views1 answer
React native andri]oid ReferenceError: Can't find variable: Intl
Javascript React
93 votes185 views6 answers
Install react router dom
Javascript React