What problem does it solve?
Releasing a new Android build of the SUB/WAVE Expo app involves choosing between a Play Store App Bundle and a sideloadable tester APK, handling EAS cloud builds, signing keystores, version codes, and OTA updates — this Skill walks through the entire release workflow correctly.
Core Features & Use Cases
- Play Store Releases: Builds a signed
.aab App Bundle with the EAS production profile, auto-incrementing versionCode, ready for manual Play Console upload.
- Tester Sideload Builds: Builds an installable APK with the
preview profile and returns a shareable install link and QR code, no Google account required.
- OTA Updates: Pushes JS-only changes over-the-air via
eas update to preview or production channels without a new binary.
- Local Build Fallback: Builds the
.aab locally when the EAS Free plan's monthly Android cloud quota is exhausted, with fixes for disk, NDK, and Metaspace failures.
- Use Case: After merging a native dependency change, run a production EAS build, download the
.aab, and upload it to the Play Console to ship the update to live users.
Quick Start
Build a new Android release of the app and give me the file to upload to the Google Play Console.