iOS simulator: snapshot drops controls nested deeper than 64 accessibility levels

クローズ
  • 何か問題がありますか？
#4,088 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

関連するプルリクエストがすでにマージされています。

  • #4089 @KrzysztofMoch による — マージ済み

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
ios, typescript
領域
mobile, testing-qa

調査の方向性

Read packages/platform-apple/src/snapshot-source/limits.ts and apple/snapshot-bridge/SnapshotBridgeCapture.m, then trace how traversal depth and the 32-request budget interact with continuations. Reproduce using the nested UIView setup described in the issue and inspect the snapshot recovery request log. Done when snapshots include nodes through depth 128, preserve behavior through depth 65, and deep chains that fit the budget complete in the bridge while budget exhaustion still fails closed.

索引モデルが issue の本文から書いたものです。

説明

On an iOS simulator, a regular snapshot stops at 65 accessibility levels (depth 0–64) and marks the tree truncated. Controls nested deeper are not in the snapshot, so press by label or ref fails with Selector did not match. React Native screens reach that depth in real apps; this came in through a downstream user of tester-army/e2e.

Repro

A UIKit app with a Deep target button under N nested plain UIViews (AX depth of the button = N + 5). Xcode 26.6, iOS 26.5 simulator, iPhone 17 Pro, main at 3b9e8d1:

UIView depth (AX depth) snapshot -i has Deep target press by label press by coordinates
20–59 (25–64) yes works works
60–120 (65–125) no Selector did not match: label="Deep target" works

The request log shows ios_snapshot_source_recovery {"producer":"simulator-ax-bridge","requestedLevels":65,…,"truncated":true}.

Cause

The simulator AX bridge already reads past the AX server's per-request limit (a request over about 62 levels fails with kAXErrorIllegalArgument) through continuations, and its protocol bound is 128 (MAXIMUM_DEPTH, kMaximumDepth). The daemon asks for less: DEFAULT_SNAPSHOT_SOURCE_LIMITS.maxTraversalDepth is 64 (packages/platform-apple/src/snapshot-source/limits.ts).

Raising the bound alone is not enough. Deeper paths need more continuations, and the 32-request budget in apple/snapshot-bridge/SnapshotBridgeCapture.m runs out on screens with several deep chains. A screen with 12 chains 100 views deep then falls back to the runner capture (5.4 s instead of 0.4 s).

Required behavior

  • A regular simulator snapshot returns nodes up to 128 accessibility levels deep.
  • For trees up to 65 levels deep, request, rejection, and continuation counts are unchanged.
  • Budget exhaustion still fails the capture closed (#2414).
  • Screens with several deep chains that fit the budget complete in the bridge, without the runner fallback.

Related

The same report also had taps failing with point.x != INFINITY && point.y != INFINITY on elements 56+ UIViews deep. That reproduces on v0.21.28 and is fixed on main by #3870 (v0.21.31): coordinate presses worked at every depth up to 120.

主要言語
TypeScript
スター
5.2k
フォーク
359
平均マージ
13時間 31分
マージ済み PR（30日）
664

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

callstack/agent-device のほかの issue

callstack/agent-device の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。