/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 vote151 views2 answers
How to sent react from data in mongodb
Javascript React
1 vote100 views1 answer
Ctx in react
Javascript React
1 vote116 views2 answers
Upload image react
Javascript React
0 vote133 views2 answers
React js http post 500 internal server error
Javascript React
0 vote144 views1 answer
React check if array contains value
Javascript React
0 vote158 views1 answer
Render blaze in react
Javascript React
2 votes118 views1 answer
What is virtual dom in react
Javascript React
1 vote121 views1 answer
React js console log not working
Javascript React
2 votes123 views2 answers
Add 2 class names react
Javascript React
2 votes160 views1 answer
Dynamic import in reactjs
Javascript React