What problem does it solve?
Releasing a new iOS build of the SUB/WAVE Expo app involves knowing when a binary is actually needed versus an OTA update, running the correct EAS commands from the right directory, and handling the manual App Store promotion step. This Skill encodes that entire release procedure so a fresh build reaches TestFlight with one command and no re-setup.
Core Features & Use Cases
- One-command release: Runs
eas build --platform ios --profile production --auto-submit --non-interactive from the app/ directory to build in the cloud and submit to TestFlight.
- OTA vs. binary decision logic: Distinguishes JS-only changes (ship via
eas update on the production channel) from native changes (dependency upgrades, patches/, config plugins) that require a new binary, using the fingerprint runtime version policy.
- App Store promotion workflow: Guides the manual App Store Connect step of attaching the processed build to a new version, including the mandatory
expo.version bump for public releases of the live app.
- Use Case: After merging a fix that touched a native dependency, ask the assistant to cut a new iOS release; it bumps
expo.version in app.json, runs the EAS build with auto-submit, and tells you when to promote the processed build in App Store Connect.
Quick Start
Ask the assistant to cut a new iOS release and push it to TestFlight using the EAS production profile.