Wait out the double-tap window in tappingCountsUp #2
Loading…
Reference in a new issue
No description provided.
Delete branch "fix-tap-test"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
One of five phone runs of the v1.0.0 pair failed tappingCountsUp on a Nokia 6.1 (API 29): the counter read "Taps: 1", expected "Taps: 2". The other four runs passed, so one of two back-to-back taps was lost. The test now checks after the first tap and waits one double-tap timeout plus 100 ms (bounded) before the second. Test change only; the app is unchanged. Needs a v1.0.1 tag build and a repeat run on phones before it counts as fixed.
Automated Codex review (read-only) of head
6a2fc2397c.No actionable findings. The delay is bounded, and the test still checks that both taps increment the counter.
BLOCKING: 0
Reviewed head
6a2fc2397cat 2026-11-18T05:10:30Z by codex exec (read-only sandbox).