📦 deps(thirdparty): update snapshots

2026-07-01 16:02:41 +00:00
parent 8301f01888
commit c824ba9d7b
2449 changed files with 555104 additions and 9259 deletions
@@ -1,29 +1,27 @@
 ---
 name: expo-dev-client
-description: Build and distribute Expo development clients locally or via TestFlight
+description: Build Expo app for development
 risk: unknown
-source: community
-version: 1.0.0
+source: https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-dev-client
+source_repo: expo/skills
+source_type: official
+date_added: 2026-07-01
 license: MIT
+license_source: https://github.com/expo/skills/blob/main/LICENSE
 ---

 Use EAS Build to create development clients for testing native code changes on physical devices. Use this for creating custom Expo Go clients for testing branches of your app.

-## When to Use
- You need an Expo development client because the app depends on custom native code or targets not supported by Expo Go.
- The task involves building, distributing, or testing EAS development builds on physical devices.
- You need guidance on when to choose a dev client versus staying on plain Expo Go.
-
 ## Important: When Development Clients Are Needed

-**Only create development clients when your app requires custom native code.** Most apps work fine in Expo Go.
+**Development clients are the recommended setup for any real or production app.** Expo Go is a playground for learning and quick experiments with the native libraries it bundles; most apps outgrow it and move to a development client. See [Expo Go vs. development builds](https://docs.expo.dev/develop/development-builds/introduction/) for the full reasoning.

 You need a dev client ONLY when using:
+
 - Local Expo modules (custom native code)
 - Apple targets (widgets, app clips, extensions)
 - Third-party native modules not in Expo Go
-
-**Try Expo Go first** with `npx expo start`. If everything works, you don't need a dev client.
+- Config plugins, or testing remote push notifications and App/Universal Links

 ## EAS Configuration

@@ -52,6 +50,7 @@ Ensure `eas.json` has a development profile:
 ```

 Key settings:
+
 - `developmentClient: true` - Bundles expo-dev-client for development builds
 - `autoIncrement: true` - Automatically increments build numbers
 - `appVersionSource: "remote"` - Uses EAS as the source of truth for version numbers
@@ -65,11 +64,13 @@ eas build -p ios --profile development --submit
 ```

 This will:
+
 1. Build the development client in the cloud
 2. Automatically submit to App Store Connect
 3. Send you an email when the build is ready in TestFlight

 After receiving the TestFlight email:
+
 1. Download the build from TestFlight on your device
 2. Launch the app to see the expo-dev-client UI
 3. Connect to your local Metro bundler or scan a QR code
@@ -80,6 +81,10 @@ Build a development client on your machine:

 ```bash
 # iOS (requires Xcode)
+## When to Use
+
+Use this skill when you need build Expo app for development.
+
 eas build -p ios --profile development --local

 # Android
@@ -87,6 +92,7 @@ eas build -p android --profile development --local
 ```

 Local builds output:
+
 - iOS: `.ipa` file
 - Android: `.apk` or `.aab` file

@@ -139,6 +145,7 @@ eas build:view
 ## Using the Dev Client

 Once installed, the dev client provides:
+
 - **Development server connection** - Enter your Metro bundler URL or scan QR
 - **Build information** - View native build details
 - **Launcher UI** - Switch between development servers
@@ -155,22 +162,26 @@ npx expo start --dev-client
 ## Troubleshooting

 **Build fails with signing errors:**
+
 ```bash
 eas credentials
 ```

 **Clear build cache:**
+
 ```bash
 eas build -p ios --profile development --clear-cache
 ```

 **Check EAS CLI version:**
+
 ```bash
 eas --version
 eas update
 ```

 ## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
+
+- Use this skill only when the task clearly matches its upstream product or API scope.
+- Verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes.
+- Do not treat generated examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
@@ -0,0 +1,4 @@
+interface:
+  display_name: "Expo Dev Client"
+  short_description: "Create and use Expo development clients when Expo Go is not enough"
+  default_prompt: "Use $expo-dev-client to decide whether an Expo development client is required, configure development EAS profiles, build local or cloud dev clients, and connect them to Metro."