callstack / callstack/react-native-pager-view

[android] when used as material-top-tab with react-navigation, navigation.navigate may not complete screen transition

Offen
#910 4 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen
android bug fabric
Vorherrschende Sprache
TypeScript
Sterne
3.4k
Forks
476
Ø Merge
10 T. 21 Std.
Gemergte PRs (30 T.)
2

Beschreibung

## 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

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start by running the linked reproducer, focusing on Bug.tsx and the material-top-tab setup that calls navigation.navigate through the drawer. Compare the transition in the new and old architectures, in development and release builds; done means the tab transition completes at the expected speed without stopping partway.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
android, react-native, typescript
Bereich
frontend, mobile
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.