React Native DeployEAS Build and Submit, on your own GitHub Actions

The same rnd commands and the same eas.json. Builds run on GitHub-hosted runners, store delivery goes through asc, and there is no Expo account or per-build fee.

Get started

Command reference

How it works

Your eas.json, unchanged

Every eas.json is resolved by a port of @expo/eas-json and checked against the real package in a differential test suite — extends chains, platform overrides, $VAR indirection and schema defaults included.

A build is a workflow run

rnd build dispatches a GitHub Actions workflow in your repo. Status, logs, timings and artifacts are the run's own; nothing sits in between.

Install on a phone from a QR code

Internal builds are published to a small Cloudflare Worker that serves an install page — itms-services on iOS, a direct APK on Android — so testers scan and install.

Ship to TestFlight

rnd submit uploads with the asc CLI using your App Store Connect API key, waits for processing and adds the build to your TestFlight groups.

Development builds with hot reload

Dev-client builds for the simulator or for registered devices, loading JavaScript live from Metro on your machine.

A dashboard that agrees with the CLI

The web dashboard and rnd build:list --json use the same mapper from workflow runs to EAS build records, so they can never disagree about a build.