react native getting old navigation parameter

Lokesh003 answered on January 7, 2022 Popularity 3/10 Helpfulness 1/10

answer react native getting old navigation parameter

react native getting old navigation parameter

Comment

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.

Popularity 3/10 Helpfulness 1/10 Language javascript

Source: Grepper

Tags: javascript navigation react-native

Link to this answer
Share Copy Link

Contributed on Jan 07 2022

Lokesh003

0 Answers Avg Quality 2/10

react native getting old navigation parameter

Contents

More Related Answers

react native getting old navigation parameter

Grepper

Documentation

Social

Legal

Contact

Oops, You will need to install Grepper and log-in to perform this action.