/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 vote137 views2 answers
Hot reload problem react 17
Javascript React
0 vote145 views1 answer
Get lat and long from address in react js
Javascript React
15 votes150 views3 answers
Image source react native
Javascript React
0 vote139 views1 answer
React native update helper
Javascript React
0 vote142 views1 answer
React how to block render if data is not fetched yet
Javascript React
24 votes203 views3 answers
Reactjs sass setup
Javascript React
0 vote150 views2 answers
Textarea react native
Javascript React
15 votes138 views1 answer
Reducer in react example
Javascript React
9 votes133 views2 answers
How to redirect react router from the app components
Javascript React
0 vote142 views1 answer
Npm: Create react chrome extension
Javascript React