agentleFS
fatihkanfatihkan/badi/.claude/skills-vault/expo-dev-client/SKILL.md

expo-dev-client

Skill8 starsChanged 3 months agoMITView on GitHub

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 launcher, scan qr, dev server.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use expo-native-ui, eas-update-insights and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • wpankSkill

    expo-native-ui

    Build beautiful native iOS/Android apps with Expo Router. Covers route structure, native tabs, animations, blur effects, liquid glass, SF Symbols, and platform patterns.

    Also in 4 projects that use this

  • nnawar706Skill

    eas-update-insights

    Check the health of published EAS Updates: crash rates, install/launch counts, unique users, payload size, and the split between embedded and OTA users per channel. Use when the user asks how an update is performing, whether a rollout is healthy, how many users are on the embedded build vs OTA, or wants to gate CI on update health.

    Also in 3 projects that use this

  • deonmenezesSkill

    expo-upgrade

    Guidelines for upgrading Expo SDK versions and fixing dependency issues

    Also in 3 projects that use this

  • arcboxlabsSkill

    expo-project-structure

    Framework (OSS). Folder structure for a new Expo app. Use when scaffolding or laying out a new Expo project with Expo Router, or deciding where a file should live in one. For new projects only — never restructure an existing app to match.

    Also in 4 projects that use this

  • CaiZongyuanSkill

    expo-ui

    This skill should be used when users need to work with Expo UI (@expo/ui) for integrating SwiftUI components into React Native applications. It provides comprehensive guidance on installation, Host component, SwiftUI primitives, layouts, modifiers, native tabs navigation, and v10 preview features.

    Also in 3 projects that use this

  • tradernetworkSkill

    eas-app-stores

    Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play. Supports Expo and other React Native projects, plus existing native apps. Use for eas.json setup, release pipelines, signing, app versions and build numbers, store submissions, and listing metadata. For Expo websites and API routes, use eas-hosting; for adding React Native screens to a native app, use expo-brownfield.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the Dev Client build and the production build are on different runtimeVersions, OTA won't apply.

    line 150

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

expo-dev-client

Setting up custom development builds with expo-dev-client. Comparison with Expo Go, build profiles, a custom dev menu, runtime-version compatibility, and the EAS Update test flow.

What It Does

  • expo-dev-client setup + build profile
  • Expo Go vs Dev Client decision
  • Dev menu (cmd+D / shake) and custom actions
  • Dev launcher (multi-app, multi-server)
  • EAS Update test flow (via the dev client)
  • Runtime version & native dep compatibility

Setup

npx expo install expo-dev-client

app.json (automatic plugin):

{
  "expo": {
    "plugins": ["expo-dev-client"]
  }
}

EAS profile:

{
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal",
      "ios": { "simulator": true },
      "channel": "development"
    }
  }
}

Build:

eas build --profile development --platform ios
eas build --profile development --platform android
# or local
npx expo run:ios
npx expo run:android

Expo Go vs Dev Client

FeatureExpo GoDev Client
SetupFrom the App StoreYour own build
Native moduleOnly Expo SDKAll custom modules
Config pluginLimitedFull support
Bundle IDhost.exp.ExponentYour own ID
Splash/iconGenericYour own
EAS Update❌✅
Push notificationLimitedFull support
Production-likeNoYes

In modern Expo the default recommendation is Dev Client. Expo Go is for quick prototyping only.

Start the Dev Server

npx expo start --dev-client
# or
npx expo start
# → the "dev client" option appears in the QR menu

Once the Dev Client app opens:

  • Show the server URL (LAN/Tunnel)
  • Scan the QR or enter the URL manually
  • The bundle loads

Dev Launcher

With the Dev Client's Switch to another bundle:

  • Connect to a different dev server (collab)
  • Preview an EAS Update branch
  • Preview the production bundle (rare)

Dev Menu

Trigger:

  • iOS sim: Cmd+D or Cmd+Ctrl+Z
  • Android emulator: Cmd+M / Ctrl+M
  • Device: shake

Menu contents:

  • Reload
  • Toggle Element Inspector
  • Toggle Performance Monitor
  • Open JS Debugger (Hermes inspector)
  • Show Dev Menu (custom button)

Custom Dev Menu Item

import { registerDevMenuItems } from "expo-dev-menu";

if (__DEV__) {
  registerDevMenuItems([
    {
      name: "Reset Storage",
      callback: async () => {
        await AsyncStorage.clear();
      },
    },
    {
      name: "Open Sentry",
      callback: () => Linking.openURL("https://sentry.io/myorg/myapp"),
    },
  ]);
}

EAS Update Test Flow

Previewing an EAS Update branch in the Dev Client:

  1. Publish an update to the branch
    eas update --branch preview --message "test"
  2. In the Dev Client app go to Extensions > Updates
  3. Select the branch, open it as a preview
  4. Return to normal mode after testing

Runtime Version Compatibility

If the Dev Client build and the production build are on different runtimeVersions, OTA won't apply. During testing:

{
  "expo": {
    "runtimeVersion": { "policy": "fingerprint" }
  }
}

The moment you add a native dep to the dev client, a new build is required. JS-only changes already arrive over the dev server.

Debug Build vs Production Build

TypeHermesJS bundleSplashDev menu
Debug (dev client)DevMetro serverNativeYes
Release (preview)ProdEmbeddedNativeNo
ProductionProdEmbeddedNativeNo

Best Practices

  • Dev client a separate build per team member (Apple device UDIDs registered)
  • Tunnel usage: npx expo start --tunnel (behind a firewall)
  • developmentClient: true profile for the dev profile only
  • Hermes turned on in dev too (same behavior as production)
  • AndroidManifest cleartext traffic is needed in dev; turn it off in production

Common Failure Patterns

  • Device can't find the dev server → not on the same LAN, or a firewall
  • "Native module XYZ doesn't exist" → the dev client was not rebuilt
  • iOS simulator dev client crash → simulator: true missing in the profile
  • Old client after a bundle ID change → uninstall + reinstall
  • Tunnel is too slow → prefer LAN or --lan

Hard Refusal

  • Distributing a production bundle via the dev client without signing
  • Registering a device UDID without the owner's permission
  • Leaving the dev menu open in production (security risk)

Output Format

  1. Build profile (development)
  2. expo-dev-client install command
  3. Start command (copy-paste)
  4. Why dev client instead of Expo Go? (rationale)
  5. EAS Update test plan

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.