Step 2: Setting Up EAS Project

First, install the EAS CLI globally if you haven't already:

npm install -g eas-cli

Log in to your Expo account:

eas login

Next, initialize EAS in your project root:

eas build:configure

This generates an eas.json file in your project. This file controls your build profiles for development, preview, and production. Here is a production configuration I frequently use:

{
  "cli": {
    "version": ">= 12.0.0"
  },
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal"
    },
    "preview": {
      "distribution": "internal"
    },
    "production": {
      "android": {
        "gradleCommand": ":app:bundleRelease"
      }
    }
  },
  "submit": {
    "production": {}
  }
}

Step 3: Building for Android and iOS

When building for Android, EAS can handle generating your keystore automatically. Just run:

eas build --platform android --profile production

For iOS, Apple requires developer accounts, provisioning profiles, and certificates. EAS handles all of this automatically as well. When you run the iOS build command for the first time, EAS will prompt you to log in with your Apple ID and will handle certificate generation for you:

eas build --platform ios --profile production

Wait for the cloud builders to finish. Once complete, you will have an .aab file for Android and an .ipa file for iOS.

Step 4: Automating Submission with EAS Submit

Instead of manually downloading binaries and uploading them via Transporter or the Google Play Console, you can let EAS submit the app for you.

For Android, you need to set up Google Play Service Account credentials. Expo guides you through linking your Google Cloud project and generating a JSON key.

For iOS, you need an App Store Connect API Key.

Once configured, submitting is as simple as:

eas submit --platform android
eas submit --platform ios

This pushes your compiled binary directly to TestFlight and Google Play Console internal testing tracks.

Common Pitfalls to Avoid

• Missing Permissions: Always declare permissions explicitly in app.json plugins (like camera, location, or notifications). If a native module uses a permission that isn't declared, Apple and Google will reject your app.
• App Icons and Splash Screens: Make sure your assets match the required resolutions. Android adaptive icons especially need proper foreground and background layering.
• Environment Variables: Use EAS Secrets (eas secret:create) to securely store API keys and environment variables instead of hardcoding them in your source code.

Ready to Launch Your Mobile App?

Publishing mobile apps doesn't have to be a frustrating bottleneck in your development cycle. By leveraging Expo and EAS, you can automate builds and deployments with just a few terminal commands.

Need help building or publishing your next React Native mobile app? Let's get in touch and talk about your project.