WWamBuildBack to project
MOBILE RELEASE CENTER

From preview to App Store and Google Play.

WamBuild prepares the native project, release configuration and signed-build workflow. You connect the store accounts once, review the result, then WamBuild can automate the repetitive release steps.

01Build

Generate an Expo / React Native app for iOS and Android from the same WamBuild project.

02Preview

Test the app in WamBuild and on a real phone before creating store binaries.

03Package

Create a signed iOS .ipa and Android .aab with EAS Build.

04Submit

Send iOS to TestFlight and Android to the selected Google Play testing track.

REQUIRED CONNECTIONS

Connect once. Reuse for every release.

Manage plugins →
Expo / EAS

EXPO_TOKEN for non-interactive builds and submissions.

Connect
Apple Developer

Developer membership + App Store Connect access.

Configure
Google Play

Play Developer account + service account key.

Configure
iOS
APPLE

App Store / TestFlight

1
Apple Developer

Connect a paid Apple Developer account.

2
App identity

Choose a unique bundle identifier such as com.company.app.

3
App Store Connect

Create the app record and connect an App Store Connect API key or Apple credentials.

4
Preview

Create an installable development/preview build and test on a real iPhone.

5
TestFlight

Build the signed .ipa and upload it to TestFlight with EAS Submit.

6
App Review

Complete screenshots, privacy, metadata and manually submit the selected TestFlight build to App Review.

AUTOMATED BUILD + TESTFLIGHT UPLOADeas build --platform ios --profile production --auto-submit --non-interactive

The automated upload lands in TestFlight. Public App Store review still requires selecting the build and submitting it for review in App Store Connect.

AN
ANDROID

Google Play

1
Google Play Developer

Connect a Google Play Developer account.

2
App identity

Choose a unique Android package name such as com.company.app.

3
Play Console

Create the app record and complete the first-time store setup.

4
Service account

Connect a Google Play service account key so WamBuild/EAS can submit builds.

5
Internal testing

Build the production .aab and submit it first to the internal testing track.

6
Production

Complete the store listing, testing requirements and promote the release when ready.

AUTOMATED BUILD + PLAY SUBMISSIONeas build --platform android --profile production --auto-submit --non-interactive

Use Internal testing first. WamBuild should not push directly to production until store setup, testing and release checks are complete.

ONE COMMAND AFTER CONNECTION

Build both stores together.

Once Apple, Google Play and Expo are connected, WamBuild can run one release pipeline for both platforms.

eas build --platform all --profile production --auto-submit --non-interactive