/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

9 votes288 views3 answers
React select
Javascript React
3 votes296 views2 answers
Whatare portals in react
Javascript React
0 vote327 views1 answer
How to make your own drop down react native
Javascript React
105 votes351 views1 answer
Install and run react js project...
Javascript React
0 vote321 views1 answer
Date picker type react
Javascript React
1 vote323 views1 answer
What is react easy emoji
Javascript React
0 vote350 views1 answer
React router remove location state on refresh
Javascript React
0 vote321 views1 answer
React toastify does not have design
Javascript React
1 vote304 views1 answer
No known class method for selector 'setScreenName:screenClass: react native
Javascript React
0 vote293 views3 answers
How to serve React JS static files with express JS?
Javascript React