expo-build-submit

Builds and uploads validated Expo apps to TestFlight and Play using EAS Build and EAS Submit.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/gmackie/agent-skills --skill expo-build-submit-gmackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: expo-build-submit
Source: https://github.com/gmackie/agent-skills/tree/main/skills/expo-build-submit
Command: npx skills add https://github.com/gmackie/agent-skills --skill expo-build-submit-gmackie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes references (resource) components.

What problem does it solve? Once an Expo app has passed validation and QA, teams still face the error-prone mechanics of choosing build profiles, sequencing platform builds, and uploading binaries to App Store Connect or Google Play. This Skill standardizes that final build-and-submit step so uploads happen with explicit profiles and clear tracking. ## Core Features & Use Cases - Profile-driven builds: Runs eas build with explicit iOS and Android profiles rather than opaque all-at-once scripts. - Store upload sequencing: Executes eas submit per platform for TestFlight, App Store Connect, or Play internal/beta/production tracks. - Readiness gating: Confirms validation, QA, and App Store review prep are complete before any upload begins. - Use Case: After QA signs off on a release candidate, ask the agent to submit the validated Expo app to TestFlight; it confirms the iOS profile and credentials, builds with the production profile, submits, and reports the build ID plus remaining review handoff items. ## Quick Start Submit this validated Expo app to TestFlight using the production profile and report the build and upload status.

Frequently Asked Questions about expo-build-submit

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

FAQPage Schema
How do I submit an Expo app to TestFlight with EAS?▼

Run eas build with an explicit iOS profile such as production, then run eas submit --platform ios with the matching profile. EAS Submit uploads the binary to App Store Connect, where it becomes available for TestFlight distribution.

How to build an Expo app for both iOS and Android using EAS Build?▼

Run eas build separately per platform with explicit profiles, for example eas build --platform ios --profile production and eas build --platform android --profile production. Platform-by-platform sequencing is preferred over a single combined script so one blocked target does not stall the other.

Does EAS Submit handle App Store review approval?▼

No. EAS Submit only uploads the build to App Store Connect or TestFlight; App Review approval is a separate later step. Review notes, demo accounts, and submission metadata may still require manual action outside EAS.

When should I not use EAS build and submit for an Expo release?▼

Do not build or submit when readiness is unresolved. Technical validation, product QA such as Maestro reports, and iOS review preparation should be completed first, since eas submit cannot substitute for readiness validation.

Why should Expo builds use explicit EAS profiles instead of defaults?▼

Explicit profiles make credential assumptions, build configuration, and destination tracks deliberate and auditable. Mixing credential setup, QA, and upload into one opaque step is a common cause of failed or misrouted submissions.