Inspect, accept, or dismiss a platform alert
alertInspect, wait for, accept, or dismiss platform permission prompts on iOS, Android, and desktop devices to automate dialog handling.
Instructions
Inspect, wait for, accept, or dismiss a platform alert. The get action reads alert content; accept and dismiss change the active alert state. Each iOS XCTest execution activates once, then only observes. Apple XCTest and Limrun iOS choose recognized English labels by preference (Allow While Using App before Allow Once); on iOS simulators, including Limrun, the runner also recognizes the device's preferred languages' wording of those labels from the OS permission-prompt strings, on any alert; equal-ranked choices and unknown labels refuse, including a lone unknown button. Open, Done, and Confirm… accept; Keep Browsing, Deny, and Skip dismiss. On the Apple XCUITest runner, dismiss taps only a recognized decline label (Cancel, Don't Allow, Ask App Not to Track, and similar) or the close element of a popover whose accessibility marker reads exactly "dismiss popup"; when no button fits the action, accept and dismiss answer ALERT_BUTTON_NOT_FOUND having tapped nothing. The get action exposes labels for explicit button targeting. The timeout argument is the poll window only for wait: a wait polls its whole window, accepted up to 2147453647 ms, and a longer one is refused before anything runs with details.reason: alert-wait-window-too-long and details.maxWaitWindowMs, never shortened. On the Apple XCUITest runner, get takes the same argument as the runner's read budget (10 s by default, at least 1.5 s, at most 25 s); other backends' get ignores it. For wait, the first XCTest read uses the requested window capped at 25 s; later reads use the remaining window with the same cap, without the 1.5 s floor. Every backend's accept and dismiss run their own retry window and ignore the argument. A get the runner's watchdog (the same budget) cuts off answers runner_main_thread_timeout with dispatched: unknown, which does not mean no alert; the next get waits out RUNNER_BUSY while abandoned work drains, and still answers RUNNER_BUSY (dispatched: no) if that outlasts the bounded resends. A get result with status none reports no alert. An alert-not-found refusal means no alert was found and no button was pressed. An alert-wait-timeout means no actionable alert resolved within the wait window. A refusal with dispatched: no means no button was activated. After a press, an unconfirmed outcome leaves the resulting alert state unknown. Times out after 90s; a caller-supplied budget extends it.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "alert"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| udid | No | Apple device or simulator UDID. | |
| action | No | ||
| device | No | Device name; ids go in udid or serial. | |
| serial | No | Android, HarmonyOS, or Vega VVD serial. | |
| session | No | Session name. | |
| noRecord | No | Do not record this action. | |
| platform | No | Device platform. | |
| timeoutMs | No | ||
| deviceTarget | No | Device form factor. |