Poor performance on Android 13 and above (re-render?) on standalone bundle

[erbud]

Current behavior

Flickering of the tab selector (material-top-tabs) and the opaque background of the Modal component, delay in touch events (Pressable) and when moving through the screens, …

Expected behavior

Fluid render as in Android 11 and earlier.

Reproduction

https://snack.expo.dev/@lya2/navigation-demo

Platform

• [X] Android
• [ ] iOS
• [ ] Web
• [ ] Windows
• [ ] MacOS

Packages

• [X] @react-navigation/bottom-tabs
• [X] @react-navigation/drawer
• [X] @react-navigation/material-top-tabs
• [ ] @react-navigation/stack
• [X] @react-navigation/native-stack
• [X] react-native-tab-view

Environment

• [] I've removed the packages that I don't use

package	version
@react-navigation/native	6.1.8
@react-navigation/bottom-tabs	6.5.9
@react-navigation/drawer	6.6.4
@react-navigation/material-top-tabs	6.6.4
@react-navigation/stack	–
@react-navigation/native-stack	6.9.14
react-native-safe-area-context	4.6.3
react-native-screens	3.22.0
react-native-gesture-handler	2.12.0
react-native-reanimated	3.3.0
react-native-tab-view	3.5.2
react-native-pager-view	6.2.2
react-native	0.72.4
expo	49.0.0
node	14.21.3
npm or yarn	6.14.18

[github-actions[bot]]

Couldn't find version numbers for the following packages in the issue:

• @react-navigation/stack

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

The versions mentioned in the issue for the following packages differ from the latest versions on npm:

• @react-navigation/native (found: 6.1.8, latest: 6.1.9)
• @react-navigation/bottom-tabs (found: 6.5.9, latest: 6.5.11)
• @react-navigation/drawer (found: 6.6.4, latest: 6.6.6)
• @react-navigation/material-top-tabs (found: 6.6.4, latest: 6.6.5)

Can you verify that the issue still exists after upgrading to the latest versions of these packages?

[erbud]

After upgrading to the latest versions of these packages, the issue persist.

[vlanemcev]

Check this issue, maybe it's related, because your described issues is similar to my case and removing specified in issue SafeAreaView for screens - helps to understand the root case.

https://github.com/th3rdwave/react-native-safe-area-context/issues/448