Use when an Expo app is already validated and you need to build or upload it with EAS Build and EAS Submit. Handles profile selection, credential assumptions, TestFlight or Play upload flow, and submission sequencing after technical readiness and QA are already complete.
Use this skill only after the app is already ready to ship.
It is for build and upload mechanics, not broad validation, not Maestro QA, and not App Store policy review. If readiness is still unclear, use expo-build-validation or react-native-expo-release-readiness first.
Establish:
For iOS, remember:
Before running eas build or eas submit, make sure:
expo-build-validationmaestro-qa-report or maestro-qaapp-store-review when relevantDo not use this skill to paper over unresolved readiness gaps.
Typical commands:
eas build --platform ios --profile production
eas build --platform android --profile production
eas submit --platform ios --profile production
eas submit --platform android --profile production
Prefer explicit profiles and explicit platform-by-platform sequencing over a giant all-at-once script.
After submission, record:
Use references/submission-sequence.md to keep the flow clear.
| Need | Action |
|---|---|
| build the release binary | eas build --platform <platform> --profile <profile> |
| upload to App Store Connect / TestFlight | eas submit --platform ios --profile <profile> |
| upload to Play | eas submit --platform android --profile <profile> |
| inspect build state | eas build:list |
eas submit as a substitute for readiness validationIf the user asks:
submit this validated expo app to testflight
do this: