Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#910 4 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
android, react-native, typescript
领域
frontend, mobile

调研方向

首先运行链接的 reproducer,重点关注 Bug.tsx,以及通过 drawer 调用 navigation.navigate 的 material-top-tab 设置。比较新旧架构中以及 development 和 release 构建中的转场;当标签页转场以预期速度完成且不会中途停止时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

android bug fabric

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

主要语言
TypeScript
星标
3.4k
派生
476
平均合并
4 天 8 小时
30 天内合并 PR
1

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

callstack/react-native-pager-view 的其他 Issue

查看 callstack/react-native-pager-view 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。