[arun279]

What happened

#204's run 39893036064 failed ui-screenshots-ios-dark (job 120217387461) on Element not found: Text matching regex: Profile. Lane health read tap proxy checked 10 taps, matched playback for 10, saw 1 cancels, tapped again 1. It was the first time the generalized re-tap fired in CI, and it double-fired.

• The re-tap: tap at 187, 502: tapped again, … backboardd: touch down without previous range event: 2 under [... "profile-to-settings" "Settings" ...], ignoring changes to frame. testmanagerd logged service canceled at 21.263, and backboardd set the touch down at 21.533, 270 ms later.
• The first touch landed:
  • backboardd logged contact 2 presence: touching at 21.533 and presence: none at 21.542.
  • The app dispatched both UIEvents to its window at 21.540 and 21.552, then logged send gesture actions at 21.557.
  • The proxy looked at the hierarchy from 21.62 to 22.04, before the push showed, found the row unchanged, and tapped again at 22.08.
  • Settings was pushed twice. The failure's screenshot shows a back button reading "Settings", so lib/back.yaml's tap on "Profile" found nothing.
• It is not the first late touch to reach the app. The earlier TV shows switch case, run 39740669724 and the switch-late fixture, logged the same lift (presence: none at 07:48:25.184) and the same two UIEvents, and that switch did not flip.

Design, replacing the one introduced in #178

The proxy plays a tap again only when the simulator log proves the tap delivered no press and nothing on screen changed. Two backboardd signatures appear in a tap's playback window:

Signature	What the app gets	Re-tap?
A cancelled contact: canceling paths contacts: [… touching …]. The digitizer went away while the contact was still down, with no lift before the cancel.	The touch, cancelled. No press fires. This is #173's Connect case.	Yes, if the elements under the point are unchanged
A late touch: touch down without previous range event after testmanagerd's service canceled	The whole touch, late. Whether the control acts is unknown: the Settings row acted, the TV shows switch did not	No, never

• Cancelled contact: a re-tap still needs the elements under the point to be unchanged on two looks: right after the tap, and 2 s later. A cancelled contact can still change what it touched; the switch in run 39722599952 toggled on one. The second look is defence in depth for a change that takes over a second to show on a slow host. It reads the hierarchy only after a cancel and costs 2 s on the rare tap it re-plays. The test below shows it holding back a re-tap.
• Late touch: it is still recorded (cancel: true, with the reason the touch may still have reached the app: …) and still named by maestro-failure.mjs when a flow fails. A late-touch flake therefore fails the lane with its cause named instead of being resent. The proxy no longer reads the hierarchy for one.

The repository's docs never listed late touches as a re-tap trigger. The only description of them was the comment in scripts/simulator-touch.mjs, which claimed the control does not act. That comment now says what the two cases show.

Tests

• Late touches never get a second tap: the TV shows switch (switch-late.txt) and Profile's Settings row (settings-late.txt, this run's playback lines) return no re-tap with the late-touch reason, even with the hierarchy unchanged. The tab bar's late touch (tab-late.txt) is the same. Through the proxy, Settings' late touch passes once with no extra hierarchy read. maestro-failure.test.ts still names a late touch.
• Cancelled contacts get one: Connect (connect-cancelled.txt), Sign out, the Profile sheet's Done and an unchanged tab bar tab are re-tapped.
• Changes still block a re-tap: the switch that toggled despite its cancel is not re-tapped, and neither is a tab that became selected. A cancel whose switch change shows only on the second look is not re-tapped either.

Mutation check:

Break	Caught by
Late touches re-tapped again (the decision uses every drop signature)	both late-touch tests
The proxy reads the hierarchy for a late touch	the proxy's late-touch test
Cancels never re-tapped	the Sign out, Done and Connect tests
No second look	the second-look test and the Done proxy test

Footprint

No product code changes. CI and tooling: scripts/simulator-touch.mjs and scripts/tap-proxy.mjs, about 40 lines added. Tests: one fixture plus the cases above.

pnpm check passes on Node 22.23.4.

[github-actions]

Pull request footprint

measurement	base to head
Product code lines in core/src, native/src, native/app, and native/modules	+0
Test lines in test, packages/*/{test,__tests__,e2e}, and .maestro	+84
CI and tooling lines in .github and scripts	+39
Product comment lines identified by a comment prefix	+0

User-delivered artifact sizes

measurement	base	head	delta
Expo iOS JavaScript bundle, raw file	5.45 MB	5.45 MB	0 B
Expo Android JavaScript bundle, raw file	5.48 MB	5.48 MB	0 B
Firebase tester APK, arm64-v8a and all densities	41.16 MB	41.16 MB	0 B
Play download estimate, XXXHDPI arm64-v8a English Android 15	19.83 MB	19.83 MB	0 B

Most complex product function

measurement	base	head
Cyclomatic complexity, oxlint complexity	10	10
Cognitive complexity, Biome noExcessiveCognitiveComplexity	15	15