/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

1 vote205 views2 answers
How to use gif in react native
Javascript React
0 vote213 views1 answer
React Update a label when rate moves
Javascript React
0 vote202 views1 answer
Relative width and height image react native
Javascript React
0 vote215 views1 answer
React hook form submit outside form
Javascript React
5 votes186 views3 answers
Linear gradient react js
Javascript React
2 votes204 views2 answers
Merge two styles react native
Javascript React
0 vote238 views1 answer
React js input autocomplete off
Javascript React
33 votes218 views2 answers
UseRef react ref
Javascript React
0 vote217 views1 answer
JSON.stringify with strip slash reactjs
Javascript React
0 vote245 views1 answer
React implicit return
Javascript React