/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 vote173 views1 answer
Connect react with database server
Javascript React
1 vote149 views1 answer
Font awesome react native icons
Javascript React
0 vote161 views1 answer
How to make your own drop down react native
Javascript React
1 vote214 views1 answer
Create functional component react
Javascript React
0 vote158 views1 answer
Detecting change in animated value react native
Javascript React
3 votes183 views1 answer
How to test on user reaction discord.js
Javascript React
0 vote143 views1 answer
Javascript slider get value react
Javascript React
0 vote160 views1 answer
Configure the Chrome debugger react
Javascript React
1 vote159 views1 answer
React material ui input max length
Javascript React
0 vote161 views1 answer
React native keyboard event listener
Javascript React