Satyajit Sahoo

Do you have `react-native-screens` enabled in your project (i.e. calling `enableScreens()`)? Can you remove it for iOS and see if fixes the issue? (or specify `detachInactiveScreens` to `false` https://reactnavigation.org/docs/stack-navigator#detachinactivescreens)

> what was the cause Seems like it's a bug in `react-native-screens` integration. You could also try updating `react-native-screens` and see if it fixes the issue.

It's only `true` by default for newer versions of `react-native-screens` which shouldn't have this bug.

@joonhocho if you have the bug with latest version of react-native-screens, can you open an issue about it in their repo, unfortuantely it's not something we can address. also a...

Can you try if this happens with latest alpha of `react-navigation-stack`?

@kaplantm can you try again with latest version of `react-navigation-stack`?

also can you post the script you're using to collect memory usage info?

You need to provide proper types like the example here: https://reactnavigation.org/docs/typescript/#specifying-default-types-for-usenavigation-link-ref-etc

Thanks for updating the PR. I'm a bit concerned about the checks using `focusedOptions`, but internally using `options` for the route. Since they don't match it can cause unexpected behavior...

Thanks for the PR. However, this change produces type errors. Can you take a look at them?