You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
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
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;
pardon me im not aware of how to put that backhandler part; i thought the
bug is navigation. navigate into a nested screen, i have no problem sliding
or using the back gesture
Environment
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
The text was updated successfully, but these errors were encountered: