callstack / callstack/react-native-pager-view
[android] when used as material-top-tab with react-navigation, navigation.navigate may not complete screen transition
- Lenguaje dominante
- TypeScript
- Estrellas
- 3.4k
- Forks
- 476
- Merge medio
- 10 d 21 h
- PR fusionados (30 d)
- 2
Descripción
## 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 https://github.com/react-navigation/react-navigation/issues/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
Guía de contribución
Línea de trabajo
Comienza ejecutando el reproductor vinculado, centrándote en Bug.tsx y en la configuración de material-top-tab que llama a navigation.navigate a través del drawer. Compara la transición en las arquitecturas nueva y antigua, tanto en builds de desarrollo como de release; se considera terminado cuando la transición de la pestaña se completa a la velocidad esperada sin detenerse a mitad de camino.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- android, react-native, typescript
- Área
- frontend, mobile
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100