subwave-app-android-release

Builds and ships Android releases of the Expo app via EAS to Google Play or testers.

1.3k|113|Updated May 11, 2026
One-click install
npx skills add https://github.com/perminder-klair/subwave --skill subwave-app-android-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subwave-app-android-release
Source: https://github.com/perminder-klair/subwave/tree/main/.claude/skills/subwave-app-android-release
Command: npx skills add https://github.com/perminder-klair/subwave --skill subwave-app-android-release

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about subwave-app-android-release

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

FAQPage Schema
How do I build an Android App Bundle with EAS for the Play Store?

Run eas build --platform android --profile production from the app directory containing eas.json. EAS builds a signed .aab in the cloud using its managed keystore and auto-increments versionCode; download it from the build page and upload it manually in the Play Console.

How do I send an Android build to testers without the Play Store?

Use the EAS preview profile with eas build --platform android --profile preview to build an installable APK. EAS returns an install link and QR code that testers open on their phones, approving the one-time unknown-sources prompt.

When do I need a new Android build versus an OTA update?

JS-only changes like components, styles, or logic ship over-the-air with eas update to the preview or production channel. A new build is required only when native inputs change, such as dependency upgrades, patches, config plugins, or app.json android settings.

What do I do when the EAS Free plan Android build quota runs out?

Build locally with eas build --platform android --profile production --local, which bypasses the cloud quota while still signing with the EAS-managed keystore. It requires the Android SDK, JDK 17, about 15 GB of free disk, and takes roughly 20 minutes.

Can I upload an AAB to the Play Store automatically with eas submit?

Not in this setup, because no Google Play service-account JSON is present on the machine, so eas submit cannot run headlessly. The .aab must be uploaded by hand in the Play Console under the app's release section.

Why can't testers install the .aab file directly on their phones?

Android phones cannot install App Bundles; the .aab format is only for Play Store upload. For direct tester installs, build an APK with the preview profile, which produces an installable file and shareable link.