Replayed taps refused with "no confirmed resting position" since 0.21.29
維護者通常 1 天內回覆
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 55/100
- Issue 類型
- 缺陷
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- android, react-native, typescript
研究方向
Start by reading the runtime gate and settle handling changes in #3631, #3570, and #3640, then compare the post-gesture settling changes in #3868, #3869, and #3915. Reproduce with the 23-test suite on an API 34 emulator, comparing 0.21.28 with the affected versions. Done means the same recordings replay without “no confirmed resting position” refusals.
由索引模型根據 Issue 內容生成。
描述
Purpose. Replaying a recorded tap on an Android Compose app stopped working reliably after 0.21.28. The tap is refused with:
ENGINE_FAILURE: The target had no confirmed resting position when the transition window after the previous action ran out, so nothing was dispatched.
The target is on screen and not moving; the screenshot at failure shows the screen fully loaded.
What we see. We replay a 23-test suite through e2e 0.21.3 and @e2e-dev/mobile 0.12.4 (strict cache) on an API 34 emulator, with the same app build and recordings for every version:
| agent-device | Result |
|---|---|
| 0.21.28 | Passes, about 15 runs with no refusals |
| 0.21.29 | Tap on an overflow button on a profile screen refused, 4 of 4 runs |
| 0.21.30 | Passed once, then a tap on the first row of a LazyColumn refused |
| 0.21.31 | Both taps refused, 2 of 2 runs |
| 0.21.32 | Both taps refused |
Both refused taps come right after a navigation (opening a tab, or opening the profile screen). It starts in 0.21.29, which moved the moving-target decision into the runtime gate (#3631) and changed settle handling (#3570, #3640). 0.21.31 and 0.21.32 changed post-gesture settling again (#3868, #3869, #3915) and it got more frequent.
Required behavior. A tap on a target that is on screen and still is dispatched, as in 0.21.28.
Done when. The same recordings replay on the new version with no "no confirmed resting position" refusals.
Dependencies. None. We are pinned to 0.21.28 until this is fixed.
- 主要語言
- TypeScript
- 星號
- 5.2k
- 分支
- 359
- 平均合併
- 12 小時 43 分鐘
- 30 天內合併 PR
- 666
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
callstack/agent-device 的其他 Issue
-
bug ready-for-agent
難度 2/5 1-3 小時 新手友好度 77/100
callstack/agent-device#4018 ·
維護者通常 1 天內回覆
-
Limrun iOS fill reports success but drops non-ASCII text可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉bug ready-for-agent
難度 2/5 1-3 小時 新手友好度 87/100
callstack/agent-device#3819 · 2 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 68/100
callstack/agent-device#1869 ·
維護者通常 1 天內回覆
-
iOS simulator: snapshot drops controls nested deeper than 64 accessibility levels可能已有人在做 @KrzysztofMoch 於 1 天前認領。 未關閉
難度 4/5 3-5 天 新手友好度 48/100
callstack/agent-device#4088 ·
維護者通常 1 天內回覆
-
needs-info
難度 5/5 一週以上 新手友好度 25/100
callstack/agent-device#4086 · 5 則留言 ·
維護者通常 1 天內回覆
查看 callstack/agent-device 的全部 Issue
相似的 Issue
-
bug ready-for-agent
難度 2/5 1-3 小時 新手友好度 73/100
PhyberApex/kuroshiro#1687 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 73/100
microsoft/monaco-editor#5563 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
bug
難度 1/5 1 小時以內 新手友好度 86/100
awslabs/visual-asset-management-system#937 ·
維護者通常 1 天內回覆
-
enhancement
難度 2/5 1-3 小時 新手友好度 72/100