Repository navigation
[android] when used as material-top-tab with react-navigation, navigation.navigate may not complete screen transition #910
Description
Environment
| package | version |
|---|---|
| @react-navigation/native | 7.0.1 |
| @react-navigation/drawer | 7.0.1 |
| @react-navigation/material-top-tabs | 7.0.1 |
| react-native-pager-view | 6.5.0 |
| react-native | 0.76.1 |
| expo | 20.0.2 |
| node | 20 |
| npm or yarn | 4 |
Description
hi! crossposted from react-navigation/react-navigation#12251
I use a custom drawer content to put buttons that navigate to specific screens as material top tabs, which are nested as a drawer screen. since the new arch migration, I observed the sliding transition of the tab screens are 1. too fast; 2. it occasionally does not do a full transition in dev, and almost never in release.
this behavior is not observed in the old arch.
Many thanks for anyone having a look at this!
see the attached video; error occurs toward the very end
https://github.com/user-attachments/assets/42b7e0b4-d784-4ae4-9595-99926aa0126b
Reproducible Demo
My reproducer is adapted from my app, but I trimmed all of my code and left only Bug.tsx as the actual reproducer.
https://github.com/lovegaoshi/azusa-player-mobile/tree/bug
Activity
rahunegix commentedon Nov 14, 2024
Hi all I found a solution and it's woking like charm look you have to follow one thing here : simply disable newArchEnabled=false in gradle properties, This is a problem with newArch
lovegaoshi commentedon Nov 14, 2024
rahunegix commentedon Nov 14, 2024
Yes this is for those who are developing things right now, So that they can continue with dev. Did you tried to do a workaround using React Native's backHandler to return false;
lovegaoshi commentedon Nov 14, 2024
github-actions commentedon Nov 13, 2026
This issue has had no activity for 180 days and is now marked as stale. It will be closed in 14 days unless there is new activity. If it still affects the latest version, please comment with a reproduction.