is: an ambiguous selector reports selector_not_found; RN text yields duplicate-label nodes
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 52/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- ios, react-native, typescript
- 領域
- mobile-dev, testing
研究方向
Start in packages/selectors/src/internal/resolution-policy.ts around lines 63-71, then reproduce the issue on the fixture app's Catalog tab using the iOS 26.2 simulator. Trace how readUnique maps non-unique matches to selector_not_found. Done means is reports a typed ambiguity outcome with the match count and the duplicate React Native text-node presentation behavior has a documented decision.
由索引模型根據 Issue 內容生成。
描述
Problem
is visible 'label="Catalog scroll: top"' fails on every run on the fixture Catalog screen (iOS Simulator, AX bridge), even on a fresh capture. get text with the same selector finds the element, and id="catalog-scroll-state" passes is visible.
Mechanism (from a live investigation on 2026-09-24, found alongside #2866/#2869):
- React Native exposes that text as a paragraph node plus a child node that carries the same label, so the label selector matches 2 nodes.
isresolves throughreadUnique(packages/selectors/src/internal/resolution-policy.ts:68-71) and refuses a non-unique match.get textresolves throughreadText(:63-66), which picks one match, so it succeeds.isthen reports the ambiguity asselector_not_found, which to an agent means the element does not exist.
Required behavior
- An ambiguous match on
isreturns a typed ambiguity outcome that names the match count, notselector_not_found. Key it on a typed reason, not on message text. - Decide whether the duplicate RN text node (parent paragraph plus child with an identical label) should be one node in presentation. That would make label selectors on RN text unique, as they read to a user.
Evidence to reproduce
Open the fixture app's Catalog tab on an iOS 26.2 simulator. is visible 'label="Catalog scroll: top"' fails every time; get text with the same selector succeeds.
- 主要語言
- TypeScript
- 星號
- 4.9k
- 分支
- 328
- 平均合併
- 12 小時 16 分鐘
- 30 天內合併 PR
- 538
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
callstack/agent-device 的其他 Issue
-
難度 1/5 1 小時以內 新手友好度 88/100
callstack/agent-device#3353 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 68/100
callstack/agent-device#1869 ·
維護者通常 1 天內回覆
-
難度 3/5 半天 新手友好度 42/100
callstack/agent-device#3360 ·
維護者通常 1 天內回覆
-
needs-triage
難度 5/5 一週以上 新手友好度 15/100
callstack/agent-device#3359 ·
維護者通常 1 天內回覆
-
難度 3/5 1-2 天 新手友好度 62/100
callstack/agent-device#3358 ·
維護者通常 1 天內回覆
查看 callstack/agent-device 的全部 Issue
相似的 Issue
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:other issue-rating: 🦞 diamond lobster no-stale P2
難度 2/5 1-3 小時 新手友好度 72/100
openclaw/openclaw#168089 · 2 則留言 · 1 個 reaction ·
維護者通常 1 天內回覆
-
✨ enhancement needs-discussion
難度 1/5 1 小時以內 新手友好度 85/100
-
[Bug]: [MCP/CLI] Bare loopback IP addresses (127.0.0.1:port) and hosts with ports fail to navigate due to erroneous scheme inference可能已有人在做 @alok-108 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 78/100
microsoft/playwright#43263 ·
維護者通常 1 天內回覆
-
area:studio type:security
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
enhancement good first issue Stellar Wave trivial
難度 2/5 1-3 小時 新手友好度 85/100
StellarCanary/ProtocolCanary-Action#331 ·
維護者通常 1 天內回覆