Expo

Get Started
Feature Preview

Creating your first build

In this guide, you'll learn how to build a ready-to-submit binary for the Apple App Store and Google Play Store using EAS Build. For a simple app, you should expect to have kicked off your builds for Android and iOS within a few minutes.

Prerequisites

EAS Build is a brand new and rapidly evolving service. It can't do everything yet, so before you set out to create a build for your project we recommend consulting the limitations page and the other prequisites below.

Don't have a project yet? No problem: it's quick and easy to create a "Hello world" app that you can use with this guide.
  • Install Expo CLI by running npm install -g expo-cli (or yarn global add expo-cli).
  • Run expo init PROJECT_NAME (let's assume PROJECT_NAME is abcd) and choose a bare workflow template (either minimal or minimal (TypeScript)).
  • EAS Build also works well with projects created by npx react-native, create-react-native-app, ignite-cli, and other project bootstrapping tools.
Terminal running expo init, with minimal (TypeScript) selected
Support for managed workflow projects is rapidly improving, but not yet ready for production, so we recommend using it with bare React Native projects for best results right now.

While EAS Build is in preview, it is available only to EAS Priority Plan subscribers. Once it graduates from preview it will become more broadly available. The first month is free, and you can cancel any time.

  • If you are going to use EAS Build to create release builds for the Apple App Store, this requires access to an account with a \$99 USD Apple Developer Program membership.

Install EAS CLI by running npm install -g eas-cli (or yarn global add eas-cli). It will notify you when a new version is available (we encourage you to always stay up to date with the latest version).

If you are already signed in through Expo CLI, you don't need to do anything. Otherwise, log in with eas login. You can check whether you're logged in by running eas whoami.

Run eas build:configure to configure your iOS and Android projects to run on EAS Build. If you'd like to learn more about what happens behind the scenes, you can read the build configuration process reference.
Additional configuration may be required for some scenarios:

  • Run eas build --platform android to build for Android.
  • Run eas build --platform ios to build for iOS.
  • Alternatively, you can run eas build --platform all to build for Android and iOS at the same time.
Before the build can start, we'll need to generate or provide app signing credentials. If you have no experience with this, don't worry no knowledge is required, you will be guided through the process and EAS CLI will do the heavy lifting.
If you have released your app to stores previously and have existing app signing credentials that you would like to use, follow these instructions to configure them.

  • If you have not yet generated a keystore for your app, you can let EAS CLI take care of that for you by selecting Generate new keystore, and then you're done. The keystore will be stored securely on EAS servers.
  • If you have previously built your app in the managed workflow with expo build:android (using the same slug), then the same credentials will be used here.
  • If you would rather manually generate your keystore, please see the manual Android credentials guide for more information.

  • If you have not generated a provisioning profile and/or distribution certificate yet, you can let EAS CLI take care of that for you by signing into your Apple Developer Program account and following the prompts.
  • If you have already built your app in the managed workflow with expo build:ios (using the same slug), then the same credentials will be used here.
  • If you would rather manually generate your credentials, refer to the manual iOS credentials guide for more information.

By default, the eas build command will wait for your build to complete. However, if you interrupt this command and monitor the progress of your builds by either visiting the EAS Build dashboard or running the eas build:show command.