Skip to content
Skills Library
Programming · Automation

dev-build-simulator

/dev-build-simulator

Start an iOS EAS Simulator session with this app's development build, connected to a live Metro dev server through the Expo tunnel, and hand the user the web preview. Use when asked for a dev build on a cloud simulator, a web preview against a live dev server, or Fast Refresh on a remote device. For Expo Go use the cloud-simulator skill instead; for anything not covered here load expo:eas-simulator.

Licence
MIT
Last repository change
29.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
5
Scripts
4
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 4 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/connect.sh, scripts/lib.sh, scripts/reconnect.sh, scripts/stop.sh

What it does and when to use it

Start an iOS EAS Simulator session with this app's development build, connected to a live Metro dev server through the Expo tunnel, and hand the user the web preview. Use when asked for a dev build on a cloud simulator, a web preview against a live dev server, or Fast Refresh on a remote device. For Expo Go use the cloud-simulator skill instead; for anything not covered here load expo:eas-simulator.

Original author description

Start an iOS EAS Simulator session with this app's development build, connected to a live Metro dev server through the Expo tunnel, and hand the user the web preview. Use when asked for a dev build on a cloud simulator, a web preview against a live dev server, or Fast Refresh on a remote device. For Expo Go use the cloud-simulator skill instead; for anything not covered here load expo:eas-simulator.

How it works

  1. 0. Check out 03-widgets
  2. 1. Start Metro with the tunnel
  3. 2. Connect the simulator
  4. 3. Stop
  5. When Metro crashes
  6. Facts for this project
Original SKILL.md headings · 57 lines, 589 words
SKILL.md preview
---
name: dev-build-simulator
description: Start an iOS EAS Simulator session with this app's development build, connected to a live Metro dev server through the Expo tunnel, and hand the user the web preview. Use when asked for a dev build on a cloud simulator, a web preview against a live dev server, or Fast Refresh on a remote device. For Expo Go use the cloud-simulator skill instead; for anything not covered here load expo:eas-simulator.
---

# Dev build on a cloud simulator with a live dev server

Four steps, each one command. Run everything from the project root in Git Bash (the Bash tool). EAS sessions cost credits, and the Metro tunnel URL is publicly reachable while Metro runs, so stop both when the task is done.

## 0. Check out `03-widgets`

The user wants the iOS web preview to run the `03-widgets` branch. Before you start Metro, run `git checkout 03-widgets`, unless the user names a different branch for this run.

If the working tree has uncommitted changes, Git carries them over or refuses the checkout. Do not stash, reset, or discard anything to force it. Tell the user which files block the checkout and ask what to do.

## 1. Start Metro with the tunnel

The tunnel exposes this project's Metro server on port 8083 so the dev build on EAS Simulator can load its bundle. Start Metro with the Bash tool and `run_in_background: true` (timeout 7200000):

```bash
EXPO_UNSTABLE_TUNNEL_V2=1 npx expo start --tunnel --dev-client --port 8083 > "$TEMP/metro-8083.log" 2>&1
```

- Do **not** set `CI=1`. It turns off file watching, so Fast Refresh stops working.
- Use port 8083. The user may run their own server on 8081; do not touch it.
- Metro serves the checked-out branch, so do step 0 first.

## 2. Connect the simulator

```bash
bash .claude/skills/dev-build-simulator/scripts/connect.sh [minutes] [name]
```

The script waits for the tunnel host, compiles the iOS bundle locally, and starts the session. In that session it installs the dev build, hides the dev menu, and opens the Metro URL. Then it attaches agent-device, waits for "Tracker", and saves `.sim/dev-build.png`. Read the screenshot to confirm the screen. Give the user the printed **web preview** URL. If `.env.eas-simulator` already has a running session, the script reuses it and only reconnects the app.

Defaults: 60 minutes, named "Live dev server web preview".

## 3. Stop

```bash
bash .claude/skills/dev-build-simulator/scripts/stop.sh
```

It stops the session, resets `.env.eas-simulator`, and stops the Metro node processes on port 8083. Stopping the background shell task alone leaves Metro running.

## When Metro crashes

This machine's DNS fails from time to time. Metro then exits with code 7 and `getaddrinfo ENOTFOUND <host>.on.expo.app` at the end of `$TEMP/metro-8083.log`. The session keeps running, but the app has no server.

1. Start Metro again (step 1). It gets a **new** tunnel host.
2. Run `bash .claude/skills/dev-build-simulator/scripts/reconnect.sh`. It points the app at the new host and passes the dev menu keys again.

Do this once. If it fails again, or agent-device reports `Remote daemon is unavailable`, stop and tell the user. Do not loop on retries.

## Facts for this project

- **Dev build:** `01f6108f-d59e-4ab5-b47f-9380d488b863`, iOS Simulator, `development-simulator` profile, built from `03-widgets`. It has every native module that `main` through `04-agentic-workflows` use, so it can load any of those branches. It expires about 90 days after 2026-10-28. To use a newer build, set `DEV_BUILD_ID`. To find one, run `npx --yes eas-cli@latest build:list --platform ios --profile development-simulator --status finished --limit 1 --json`. If a branch adds native code, that branch needs a new dev build.
- **App:** bundle ID `com.keithco.cdmx2026demoapp`, URL scheme `cdmx2026demoapp`. Every branch shows "Tracker" on launch.
- **Fast Refresh check:** edit a visible string, wait for it with `simulator:exec agent-device wait text "..."`, then revert the edit with `git checkout -- <file>`. Using `sed` to revert leaves a CRLF-only diff.
- **Run agent-device only through `npx --yes eas-cli@latest simulator:exec`.** Called directly, it does not load the session settings and can use a local simulator by mistake.
Files in this package (5)
  • SKILL.md 4 KB
  • scripts/connect.sh 2 KB
  • scripts/lib.sh 3 KB
  • scripts/reconnect.sh 1 KB
  • scripts/stop.sh 1 KB

Versions

The database has no other skills named dev-build-simulator.

Database snapshot: 13.11.2026 · package version 66f486ac558f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100cloud-simulator
    Run this app on an iOS EAS cloud simulator in Expo Go and drive it with the globally installed agent-device, from this Windows machine. Use when asked to run, screenshot, or click through the app on a simulator or device. Project-specific adaptation of the expo:eas-simulator…
  • 90expo-ios-simulator
    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…
  • 100limrun-expo-development
    Prepare and run Expo / React Native apps on Limrun with Expo dev-client iteration. Use when the user wants an Expo dev build, Metro tunnel, hot reload, JS/TS iteration without repeated native rebuilds, or to run/test an Expo app on a remote iOS simulator or Android emulator.
  • 100eas-simulator
    Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any `eas simulator:*` commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud…
  • 91ios-simulator
    Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
  • 100expo-dev-client
    Custom development builds with expo-dev-client, build profiles, a custom dev menu, runtime-version compatibility, and EAS Update integration. Triggers on expo-dev-client, dev client, custom dev build, development build, dev menu, expo go, runtime version, debug build, dev…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.