Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

iOS: tapping a Flutter password field records an XCTest failure and restarts the runner, although the tap lands

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

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

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
57/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
flutter, ios
領域
mobile-dev, testing-qa

調査の方向性

Reproduce the sequence with agent-device open, snapshot -i --force-full, and click @e6, then inspect the runner's post-dispatch lookup and tap-failure corroboration path described in the logs. Compare the password-field behavior with the email field and verify that a landed tap no longer returns XCTEST_RECORDED_FAILURE or invalidates the runner session.

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

説明

Summary

On the iOS Simulator, every tap on a Flutter password field returns XCTEST_RECORDED_FAILURE.

The tap lands. The field takes focus, and a following type enters the text.

But the failure invalidates the runner session. Each tap then costs 7 to 14 seconds instead of under 1 second. The tap-failure corroboration from #1605 runs, and then rejects the tap with ios_tap_failure_corroboration_identity_mismatch.

#1599 asks for a narrow issue when a current sequence reproduces this failure, so here is one.

Version

  • agent-device 0.21.15, both CLI and daemon.
  • macOS host, iPhone 17 simulator on the iOS 26.0 runtime. The runner is built against iphonesimulator26.5.
  • The app is a Flutter app. Its login screen has an email TextField and a password TextField with obscureText: true.

I have not run this on 0.21.16. The commits in v0.21.15...v0.21.16 do not touch tap corroboration or the runner's post-tap lookup.

Steps

agent-device open <flutter-app> --relaunch --platform ios
agent-device snapshot -i --force-full
# @e5 [text-field] "Email" [editable]
# @e6 [text-field] "Password" [editable]
agent-device click @e6 --json

What we measured

All commands ran on the same login screen, each from a fresh relaunch.

command result duration
click @e5 (email field) ok 0.7 to 1.2 s
click @e6 (password field), keyboard down XCTEST_RECORDED_FAILURE 12.8 s
click @e6 XCTEST_RECORDED_FAILURE 7.7 to 8.5 s
press 201 406 (centre of the password field) XCTEST_RECORDED_FAILURE 7.1 s
fill @e6 <text> XCTEST_RECORDED_FAILURE ("while executing type") 4.5 s

Two runs of our agent hit the same failure on this screen, costing 13.8 s and 7.5 s.

The result does not depend on the keyboard. It fails with the keyboard down and after typing into the email field. The email field on the same screen taps normally.

The tap lands

After a failed click @e6, type abc123 returns Typed 6 chars. A screenshot then shows the password field focused, with the masked text and the keyboard up.

Where the failure comes from

The runner dispatches the tap first. The failure comes from a lookup that runs after it:

AGENT_DEVICE_RUNNER_SYNTHESIZED_DISPATCH kind=tap point=(201.0,406.0) reference=(0.0,0.0,402.0,874.0) orientation=1
    t =    12.52s Find the "Password" TextField
    t =    13.55s     Find the "Password" TextField (retry 1)
    t =    14.58s     Find the "Password" TextField (retry 2)
    t =    14.68s     Find: Descendants matching type TextField
    t =    14.68s     Find: Element at index 1
<unknown>:0: error: -[AgentDeviceRunnerUITests.RunnerTests testCommand] : Failed to get matching snapshot: No matches found for Element at index 1 from input {(
    TextField
)}
Possibly caused by runtime issues:
Automation type mismatch: computed TextField from legacy attributes vs Other from modern attribute. Input attributes and values: {
    "XC_kAXXCAttributeAutomationType" = 0;
    "XC_kAXXCAttributeElementBaseType" = UIAccessibilityElement;
    "XC_kAXXCAttributeElementType" = TextInputSemanticsObject;
    "XC_kAXXCAttributeTraits" = 146029150208;
}
AGENT_DEVICE_RUNNER_TARGET_CACHE_INVALIDATE reason=xctest_recorded_failure

Flutter's TextInputSemanticsObject reports TextField through the legacy attributes and Other (automation type 0) through the modern one. So a query by element type TextField finds nothing, and XCTest records a failure.

The request log for the same tap shows where the time goes:

phase duration
ios_runner_command_send (tap, including the three lookup retries) 2951 ms
ios_runner_session_invalidated, reason xctest_recorded_failure
runner restart (ios_runner_connect retries) 4046 ms
snapshot_capture for corroboration 4140 ms
ios_tap_failure_corroboration_identity_mismatch
request_failed XCTEST_RECORDED_FAILURE

Expected

A tap that was dispatched and landed should not fail the command. At minimum, it should not end the runner session.

We don't know the runner's internals, but two changes would each remove the cost here:

  • The post-dispatch lookup should not be able to record a test failure. For example, it could match by frame or identifier rather than by element type, or treat a miss as non-fatal.
  • Corroboration should accept the tap when the focused element changed to the tapped field. Here, corroboration seems to compare against an identity that includes this unstable type.

Workaround

When a tap fails with XCTEST_RECORDED_FAILURE ("while executing tap") right before we type, we type anyway and flag the tap as unconfirmed.

Related: #1599, #1605, #2273.

主要言語
TypeScript
スター
4.8k
フォーク
315
平均マージ
11時間 27分
マージ済み PR（30日）
556

環境構築

はじめの一歩

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

callstack/agent-device のほかの issue

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

似ている issue

TypeScript の issue をもっと見る

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

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