Satyajit Sahoo

> The code snippet in codesandbox is trying to say, we should not call setState directly in function body. It needs to provide a valid reason to say that. The...

effects run asynchronously. it's possible that there was a state change/navigation before the effect could run. however, it's an edge case and the logic handles that. i don't know how...

@kkafar this behavior now being default with `navigate` only makes it easier to see the problem, but it's not the only way to surface the issue (e.g. you can also...

@dcporter did you read Dan's comment? where he gives this example: The developer imports a module for side-effects: ```js import 'some-module'; ``` Later they want to import something else from...

You can try clearing npx cache, e.g. `npx clear-npx-cache`

Fixed via https://github.com/react-navigation/react-navigation/commit/c2caf87bc5df50f665442fbb0c42794cad793a3a

Bottom Tabs does dispatch this action on blur. You can see that there's no animation when using `@react-navigation/stack`. This seems to be an issue in native stack where it doesn't...

I can repro this. We're always passing `topInsetEnabled: true` to react-native-screens, but somehow it doesn't render correctly on first render. Seems like there's a bug in `react-native-screens` regarding this. https://github.com/user-attachments/assets/6bf1b2f5-d33e-4aac-addb-69bd219ba859

@hirbod there's a PR in screens repo to ignore `statusBarTranslucent` when using edge to edge https://github.com/software-mansion/react-native-screens/pull/2464

@lucasmrl that PR doesn't fix this issue. please open a bug report in react-native-screens repo unless someone already has, so that it can be tracked there and fixed.