/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 vote438 views1 answer
React native progress bar slider
Javascript React
91 votes430 views7 answers
React-router-dom
Javascript React
1 vote358 views1 answer
Adding int and string in react props
Javascript React
0 vote364 views1 answer
Const userMessage Reaction = new UserMessage Reaction({ _id: mongoose.Types.ObjectId(), userId: "USERID", userName: "TESTUSERNAME", messageId: "TESTMESSAGEID", time: "TESTTIME" });
Javascript React
2 votes369 views1 answer
Site cannot be accessed broken link or url that doesn’t exist react netlify
Javascript React
0 vote374 views2 answers
React write into json file
Javascript React
9 votes318 views4 answers
Firebase' is not defined no-undef react
Javascript React
1 vote332 views1 answer
Mui modal backdrop
Javascript React
0 vote392 views3 answers
Proptypes for a react component
Javascript React
0 vote354 views1 answer
React type div onClick
Javascript React