Skip to content

simiancraft/simiancraft-skills / skills/expo-ios-simulator

expo-ios-simulator

Verified

Run and drive an Expo / React Native app on the iOS Simulator. Pick an execution mode (Expo Go, dev client, Storybook-mobile, web-on-mobile), build and install a dev client, and clear the recurring Expo/RN prompts that block automation: the push-token alert that stacks until the overlay darkens the screen, the "Open in app?" deep-link dialog, the dev menu, and the element-inspector trap. Sits ON TOP of ios-simulator; failures route to ios-simulator-triage. Project-agnostic; discovers bundle id and scheme from the app config. Use for "run my Expo app on the simulator", "load a dev client", or "drive Storybook on iOS".

FileKindSize
SKILL.mdskill md3.8 KB
references/development-builds.mdmarkdown4.4 KB
references/execution-modes.mdmarkdown2.1 KB
references/expo-go.mdmarkdown3.2 KB
references/known-prompts.mdmarkdown5.3 KB

references/known-prompts.md

View on GitHub
---
title: Known prompts and overlays
summary: the recurring Expo/RN dialogs and overlays that block automation, and how to clear each by accessibility (axe tap --label), including the stacking push-token alert, the LogBox toast, and the element-inspector trap
status: complete
sources:
  - "axe describe-ui output of the Expo dev menu (labels for this writing; re-run describe-ui to confirm, they drift across Expo/RN versions)"
  - "Simulator Device menu > Shake and its Cmd+Ctrl+Z accelerator, a Simulator-level command (see ios-simulator references/simulator-ui.md)"
  - "Observed, reproducible: the push alert re-fires and stacks on each reload; the element-inspector overlay intercepts taps until toggled off"
  - "Observed, reproducible: the LogBox toast is a single GenericElement with no AXUniqueId and no separately addressable close button; tapping its body opens the full-screen inspector"
  - https://reactnative.dev/docs/debugging (LogBox, the in-app warning and error display)
  - https://docs.expo.dev/debugging/tools/ (the Expo dev menu and its tools)
---

# Known prompts and overlays

Reference for **expo-ios-simulator**. Launching and reloading an Expo app raises native
dialogs and overlays that stall automation. Clear each by **accessibility**, not
coordinates: `axe describe-ui` to read the label, then `axe tap --label "<label>" --udid <udid>`
(every AXe command needs `--udid`; see **ios-simulator** `references/driving.md`). The
`cliclick` coordinate path is a last resort only.

## The launch sequence

1. **"Open in '<App>'?"** system dialog, from the dev-client deep link (see
   `development-builds.md`). Dismiss: `axe tap --label "Open" --udid <udid>`.
2. **"Must use physical device for Push Notifications"** alert, the push-token alert; it
   fires because the app requests a native APNs device token (`getDevicePushTokenAsync`),
   which a simulator cannot vend. A simulator on Xcode 14+ can still receive a remote push and
   an Expo push token, and `xcrun simctl push` can deliver a payload; the missing piece is the
   native device token. Dismiss it with
   `axe tap --label "OK" --udid <udid>`. It re-fires on every reload, so the alerts stack;
   after a reload, dismiss them in a loop until none remain, otherwise the stacked overlays
   darken and block the screen:

   ```bash
   while [ "$(axe describe-ui --udid <udid> | jq '[.. | objects | select(.AXLabel? == "OK")] | length')" -gt 0 ]; do
     axe tap --label "OK" --udid <udid>; sleep 1
   done
   ```

## The LogBox toast

A runtime warning or non-fatal error raises **LogBox**'s dark toast pinned to the bottom of
the screen (a count, the message, and an X). It does not intercept taps elsewhere, but it
covers whatever sits under it (a tab bar, a footer button), and **tapping its body opens the
full-screen LogBox inspector**, which does block the app. The toast is one `GenericElement`
with no `AXUniqueId` and no separately addressable close button, so this is a legitimate use
of the coordinate fallback: read the toast's `frame` object from `describe-ui` (see the key
names in **ios-simulator** `references/driving.md`) and tap the X at its right edge (about
24 points in from the right, vertically centered). The toast's label shape varies with the
issue kind (observed: `3, <message>` for a counted error or warning, `! <message>` for a
promise-rejection warning), so read the actual label from the tree rather than assuming a
prefix; both observed shapes match:

```bash
axe describe-ui --udid <udid> | jq -c '.. | objects | select(.AXLabel? // "" | test("^([0-9]+, |! )")) | .frame'
axe tap -x <frame.x + frame.width - 24> -y <frame.y + frame.height / 2> --udid <udid>
```

If the full-screen inspector opens by accident, its own dismiss controls are labeled; read
them with `describe-ui` and tap by label.

## The dev menu

Open it with the Simulator's Device > Shake accelerator **Cmd+Ctrl+Z** (a Simulator-level
command, see **ios-simulator** `references/simulator-ui.md`; it works even when app-level
keys do not reach the app). `axe describe-ui` then shows its
labels: `Reload`, `Go home`, `Toggle performance monitor`, `Toggle element inspector`,
`Open JS debugger`, and `Close`, plus `Connected to: http://localhost:8081`. Drive any of
them by label, for example `axe tap --label "Reload" --udid <udid>`; close it with
`axe tap --label "Close" --udid <udid>`. This file is only the iOS way to open and drive the
menu; for what each item does (the performance monitor's two-thread FPS, the element inspector's
modes, Open DevTools), see **expo-developer-tools** `references/dev-menu.md`, the shared home for
the menu and React Native DevTools.

## The element-inspector trap

If `Toggle element inspector` gets toggled on (easy to do by accident), the app shows a
dark "inspect" overlay and taps stop reaching the app. Recover by re-opening the dev menu
(Cmd+Ctrl+Z, or click Device > Shake via AppleScript if the keystroke does not land, see
**ios-simulator** `references/simulator-ui.md`) and tapping it off with
`axe tap --label "Toggle element inspector" --udid <udid>`.

## See also

- **ios-simulator** `references/driving.md`: `axe describe-ui` and `axe tap --label`.
- **expo-developer-tools** `references/dev-menu.md`: what each dev-menu item does (shared iOS/Android).
- `development-builds.md`: the deep link that raises the "Open in" dialog.
- **ios-simulator** `references/simulator-ui.md`: the Simulator menus behind the shake shortcut.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall