You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e446500
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ios): keep alert activation out of XCTest's interruption handling
Before every event XCTest looks for SpringBoard banners and alerts over the target and runs its
interruption handler on them. For a notification banner the default handler waits up to 15 s for
it to leave, so an `alert accept` issued while a banner was visible tapped after the command's
deadline and answered ALERT_DEADLINE_EXCEEDED for a button it had in fact pressed (#2546's late
tap, from the banner side). Four iOS CI failures of the alert replacement tests carry this trace,
including main job 106127169259: banner wait from t=7.98 s, tap at t=15.12 s on a ~15 s deadline.
`withBoundedInteractionIdleTimeoutIfSupported(.preEventSkipped)` drops only the idle wait. Alert
activation now also sets XCUIApplication's `doesNotHandleUIInterruptions` on the alert's owner app
for the one tap. It keeps the XCTest coordinate tap and its post-event settle, which alert
verification relies on; the synthesized-event path would have dropped that settle too.
The runner host app gains a `--agent-device-alert-banner` fixture that keeps a notification banner
over its alert until the alert is answered. The new test fails on the old dispatch with the CI
signature (interruption monitors consulted, ALERT_DEADLINE_EXCEEDED after the button was activated)
and passes with the opt-out.
0 commit comments