Release with EAS

📡 What you will learn

• Using Expo Application Service to compile and sign Android/iOS apps with custom native code

Identify the differents areas of the Expo Ecosystem:

• Project bootstrapping / run 👉 Expo CLI
• Adding new features 👉 Expo SDK
• Building and Signing 👉 EAS Build
• Submitting 👉 EAS Submit
• Hotfixes 👉 EAS Update

👾 Before we start the exercise

Visit expo.dev/eas and Sign up to start using EAS. The free plan already includes everything you need if you are an indie hacker working on your own apps.

In addition, to release in production to the stores, you need to have an account for:

• iOS on App Store Connect $99 per year
• Android on Google Play Store $30 one time payment

👨‍🚀 Exercise 1

Setup

To use EAS, you will need to install the eas-cli package globally. Go to your terminal and run the following command.

npm i -g eas-cli
eas login

Init

eas init
✔ Linked to project @weshipit/spacecraft
✔ Linked app.json to project with ID 012aaaa3-4ce5-4bae-9f4d-2f842489f07a

Build

Create your first build

eas build:configure

After finishing this configuration. You will get a new eas.json file in the root directory of your current project.

eas build
✔ Select platform › Android
✔ Linked to project @weshipit/spacecraft
✔ Using remote Android credentials (Expo server)

⌛ 30 min

On your Expo account, you should have someting like this:

Submitting your app to the store

eas submit
✔ Select platform › Android
✔ Linked to project @weshipit/spacecraft

EAS will use your latest build for the submission by default, but you can manually specify a previous build if you want.

If you are stuck, run eas submit --help from the terminal to get informations.