simiancraft/simiancraft-skills / skills/expo-ios-simulator
expo-ios-simulator
VerifiedRun 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".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.8 KB |
| references/development-builds.md | markdown | 4.4 KB |
| references/execution-modes.md | markdown | 2.1 KB |
| references/expo-go.md | markdown | 3.2 KB |
| references/known-prompts.md | markdown | 5.3 KB |
references/expo-go.md
View on GitHub---
title: Running under Expo Go
summary: the Expo Go path on the simulator (npx expo start, press i, auto-install) and the fixed-native-set limit that forces a dev client for any app with custom native code
status: complete
sources:
- https://docs.expo.dev/get-started/set-up-your-environment/ (npx expo start; press i; Expo CLI installs Expo Go automatically)
- https://docs.expo.dev/develop/development-builds/introduction/ (Expo Go ships a fixed set of native libraries; custom native code cannot be added; when to switch to a dev build)
---
# Running under Expo Go
Reference for **expo-ios-simulator**. Expo Go is the prebuilt Expo client from the App
Store: the fastest way to put a **pure-JS** Expo app on the simulator, and the wrong
tool the moment the app carries custom native code. For the dev-client path it forces
you onto, see `development-builds.md`; for choosing between the modes, `execution-modes.md`.
## Launching an app in Expo Go
Expo CLI installs and drives Expo Go for you; you do not build anything.
```bash
npx expo start # start Metro (no --dev-client)
# press i to open the iOS Simulator
```
Expo CLI **installs Expo Go automatically** on the booted simulator, then opens the app
inside it. If several simulators are booted, target one first (see **ios-simulator**
`references/lifecycle.md`); pressing `i` acts on the active simulator.
## The hard limit: a fixed set of native modules
Expo Go ships **a fixed set of native libraries built in** (for example
`react-native-webview`). That native bundle is whatever was uploaded to the App Store;
it cannot be extended at runtime. The Expo docs put it plainly: *"There is no way to get
the native code into the Expo Go app unless it was already included in the bundle that
was uploaded to the app stores."*
So when an app imports a native library outside that set (a `react-native-firebase`, a
custom Expo Module, anything with its own Swift/Obj-C), the **JavaScript still runs but
errors the instant it calls the missing native code**. The failure is not a build error;
it is a runtime crash on first use, which is why it is easy to mistake for an app bug.
Triage of that symptom lives in **ios-simulator-triage** `references/runtime-failures.md`.
## When Expo Go is the wrong mode
Per the Expo docs, you need a **development build** (not Expo Go) to:
- use any native library outside Expo Go's fixed set, or a config plugin;
- test app icon, name, or splash-screen changes;
- exercise remote push notifications;
- exercise App / Universal links;
- support older SDK versions on a device.
Expo positions Expo Go as *"a playground app for students and learners"*; a real app with
native dependencies belongs on a dev client. If you are unsure which the project is, check
the app config and `package.json` for native modules or config plugins, then default to
`development-builds.md`.
## See also
- `development-builds.md`: the dev-client build the native-set limit forces you onto.
- `execution-modes.md`: Expo Go versus dev client versus Storybook-mobile versus web.
- **ios-simulator-triage** `references/runtime-failures.md`: the missing-native-module crash.
- **ios-simulator** `references/lifecycle.md`: targeting one of several booted simulators.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |