Flaky Android Expo Detox E2E: native greeting never shows up / app drops Detox connection
维护者通常 4 天内回复
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- android, github-actions, react-native, typescript
- 领域
- ci-cd, mobile-dev, testing
调研方向
Start by downloading the Detox Android artifacts from the linked failed CI runs and inspect logcat-full.txt for a crash or ANR around the reported failures. Compare logs from both failure modes and the Vanilla job to see whether they share a cause. Done means identifying and reproducing the root cause on the matching CI emulator; collecting tombstones is suggested as an additional diagnostic.
由索引模型根据 Issue 内容生成。
描述
The Detox E2E (AndroidApp - Expo XX) jobs keep failing on both Expo 57 and 58, on main and on PRs. Both tests in the suite fail together, so the job goes red each time it happens.
There are two ways it fails:
- The native greeting never shows up. In
beforeAll, the app process starts (Android app process is up), butHello native Android (Expo XX)never appears in UIAutomator. After ~90s it fails withTimed out waiting for UIAutomator to contain any of: Hello native Android (Expo 58), ....- #487
9847a70, Expo 58: https://github.com/callstack/react-native-brownfield/actions/runs/38875620919/job/116900216109 - #494
41c5e84, Expo 57: https://github.com/callstack/react-native-brownfield/actions/runs/38797744225/job/116674197865
- #487
- The app drops the Detox connection after opening the Expo RN screen. The greeting is fine, then
Opening the Expo RN screen...→Detox can't seem to connect to the test app(s)!, which looks like the app crashed.
Also this one, where it lost the connection right after the process came up, before the greeting check finished: #487 e0f5940, Expo 57: https://github.com/callstack/react-native-brownfield/actions/runs/38458013604/job/115565183435
So my guess is the app is crashing in all of them, just at different moments. The failed jobs already upload the full host-side logcat (logcat-full.txt, added in #473) together with the other Detox artifacts (#466), in the detox-androidapp-<flavor>-<flavor>-android artifact. I haven't gone through those logs yet to confirm a crash.
The Android road test & E2E (AndroidApp - Vanilla) job fails the same way as (1): it waits for Hello native Android and all 4 tests time out. That one has failed on main d28810c, #494 and #487, so it might be the same root cause:
https://github.com/callstack/react-native-brownfield/actions/runs/38857242075/job/116831993012
To do:
- go through
logcat-full.txtfrom the failed runs' artifacts and look for a crash / ANR - consider also pulling tombstones (
/data/tombstones) on failure (not collected yet) - try to repro locally on the same emulator image (API level / ABI as CI)
- 主要语言
- TypeScript
- 星标
- 552
- 派生
- 53
- 平均合并
- 3 天 13 小时
- 30 天内合并 PR
- 16
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
callstack/react-native-brownfield 的其他 Issue
-
Android: generated ReactNativeHostManager loads React Native twice and crashes (Feature flags cannot be overridden more than once)可能已有人在做 @hurali97 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
callstack/react-native-brownfield#492 · 1 条评论 ·
维护者通常 4 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
callstack/react-native-brownfield#498 ·
维护者通常 4 天内回复
-
难度 4/5 3-5 天 新手友好度 55/100
callstack/react-native-brownfield#468 ·
维护者通常 4 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
callstack/react-native-brownfield#420 ·
维护者通常 4 天内回复
-
难度 5/5 一周以上 新手友好度 38/100
callstack/react-native-brownfield#406 ·
维护者通常 4 天内回复
查看 callstack/react-native-brownfield 的全部 Issue
相似的 Issue
-
backend priority:P3 privacy-fix
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
bug desktop v3 windows
难度 2/5 1-3 小时 新手友好度 65/100
esengine/DeepSeek-Reasonix#13697 · 1 条评论 ·
维护者通常 1 天内回复
-
area:security documentation effort:S priority:P2
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
app:web meta:ops
难度 2/5 半天 新手友好度 78/100
osu-tournament-rating/otr#1113 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 82/100