void-eas-build-profile

Configures eas.json build profiles for Expo apps with per-variant env, signing, and distribution settings.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-eas-build-profile-voidcorp-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: void-eas-build-profile
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/cli/core-assets/packs/pack-mobile/skills/void-eas-build-profile
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-eas-build-profile-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Expo's default eas.json scaffold leaves developers guessing which options matter for each build profile, leading to misconfigured signing, leaked secrets in bundles, and the inability to install dev and production variants side by side. This Skill ships a proven 3-profile convention (development, preview, production) with the reasoning behind every option. ## Core Features & Use Cases - 3-Profile eas.json Template: Provides development, preview, and production profiles with correct distribution channels, build types (APK vs AAB), simulator targets, and autoIncrement settings. - Variant-Based App Configuration: Uses the APP_VARIANT environment variable with app.config.ts to switch bundle IDs, app names, and API URLs so all three variants install on one device. - Secrets and Signing Guidance: Explains how to keep secrets out of eas.json using eas secret, configure credentials with eas credentials, and set up submit config for one-command store submission. - Use Case: A mobile team needs QA to test a preview build against staging APIs while production stays installed on the same phone. Apply this Skill to generate the eas.json profiles and app.config.ts variant logic that make side-by-side installs work. ## Quick Start Ask the agent to configure EAS Build profiles for your Expo app using the development, preview, and production convention with per-variant bundle IDs.

Frequently Asked Questions about void-eas-build-profile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure eas.json profiles for an Expo app?

Define three build profiles in eas.json: development with developmentClient and simulator builds, preview with internal distribution for QA, and production with store distribution and autoIncrement. Each profile sets its own env variables and build type.

How to install dev and production Expo builds on the same device?

Set an APP_VARIANT env variable per profile and use it in app.config.ts to generate distinct bundle identifiers and package names per variant. Different bundle IDs let iOS and Android treat each variant as a separate app.

Should I use APK or AAB for EAS Build Android profiles?

Use APK for development and preview profiles because APKs install directly on devices and are easier to share with stakeholders. Use the default AAB (App Bundle) for production since the Play Store requires it.

Can I put API keys in the eas.json env block?

No, values in the eas.json env block are baked into the JavaScript bundle and are publicly extractable. Use eas secret:create for server-side build secrets like NPM_TOKEN, which EAS injects into the build environment only.

Why does my EAS production build get rejected for duplicate version codes?

Stores require a unique buildNumber (iOS) or versionCode (Android) per submission. Enable autoIncrement: true in the production profile so EAS bumps these values automatically on every build.

How do I test an EAS Build configuration without spending build minutes?

Run eas build with the --local flag, for example eas build --profile preview --platform ios --local. A successful local build means the EAS cloud build will succeed with the same configuration.