/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 vote155 views1 answer
React native run on a particular emu
Javascript React
4 votes184 views2 answers
How to take 100% width in react native
Javascript React
16 votes114 views1 answer
How to insern an image in react
Javascript React
3 votes213 views1 answer
React create array
Javascript React
0 vote185 views1 answer
Reactive forms change event in angular
Javascript React
1 vote152 views2 answers
React native get timezone
Javascript React
105 votes214 views1 answer
Install and run react js project...
Javascript React
0 vote186 views1 answer
React native get route name
Javascript React
0 vote166 views1 answer
React native text input right
Javascript React
1 vote164 views1 answer
React native basic template
Javascript React