itsfolf/eas-gha

Running EAS locally in GitHub actions

EAS in GitHub Actions

Build your apps with EAS, without using EAS

Structure  —  Workflow  —  How to use it  —  Caveats

📁 Structure

The app is based on the tabs template, just as example.

👷 Workflow

The workflow is a simple GitHub Actions workflow using expo-github-action, eas build --local command, and uploading artifacts to the workflow run.

🚀 How to use it

By default, the workflow is only running when you trigger it manually. But you can customize it however you like. Just make sure you are running the eas build --local command with the right --platform and --profile flags.

⚠️ Caveats

Using macOS to support iOS builds

Ubuntu is the fastest environment of GitHub Actions, but to support iOS builds we need to use macOS. You can optimize this by changing the OS per platform.

Colon in binary names

Right now, the local app binary has a name with a colon. actions/upload-artifact doesn't accept colon in files, so we need to rename it before uploading. (more info here)

One platform per run

As of writing, the eas build --local command can only build a single platform per execution. You can run it multiple times in your workflow, but only for a single platform per run.

Using local credentials in CI

If you want to fully disconnect from Expo services, you'll need to maintain the keystore or certificates yourself. You can do that by configure EAS with local credentials. When your CI provider doesn't allow you to add "secret files", like GitHub Actions, you can encode these files to base64 strings and decode whenever you need it.

It's highly recommended to keep keystores and certificates out of your repository to avoid security issues.

with :heart:  byCedric