Guides › CI/CD for React Native and Expo apps
CI/CD for React Native and Expo apps
5 min read
CI/CD for React Native and Expo usually stalls on the build itself: Android needs an SDK and a keystore, iOS needs a Mac. BuildStack moves the build to the cloud and exposes it as a plain HTTP API, so any CI can trigger a signed build without hosting a build machine.
Trigger from GitHub Actions or any CI
Because it is a plain HTTP API, there is no marketplace action to adopt and no build config to learn. The same curl call runs from GitHub Actions, GitLab CI, your own self-hosted runners or a CLI, so you keep the pipeline you already have.
# .github/workflows/release.yml
- name: Build & sign with BuildStack
run: |
curl -sfX POST "https://api.mybuildstack.com/api/projects/$PROJECT/builds" \
-H "Authorization: Bearer ${{ secrets.BUILDSTACK_KEY }}" \
-d '{"variant":"release","format":"aab","sign":true,"publish":"internal"}'
env:
PROJECT: ${{ vars.BUILDSTACK_PROJECT }}
Signing happens on the runner
Signing is applied on the build runner from managed credentials: your Android keystore is sealed at rest and Apple credentials are managed for you. A build with sign set to true is signed without any secret passing through your CI, so you never store a keystore in the repo or in CI variables.
Billed on build minutes
Builds are billed on build minutes rather than per build, so a fast Android build costs less than a long iOS archive. The free tier covers 25 Android, 2 iOS and 5 Windows desktop builds a month with no card, which is enough to wire the pipeline up before you commit.
Workspaces, roles and shared quota
A team workspace keeps projects, signing credentials and API keys in one place, with members and roles so access is shared without passing secrets around, and build minutes drawn from a shared quota. Crash reporting and over-the-air updates through release channels round out the release loop once a build ships.
Self-hosted runners when you need them
The same API drives self-hosted runners, so you can run builds on your own hardware while keeping managed signing and the publish targets. The call is identical; only where the build executes changes.
To wire this in, create a workspace to get a project id and an API key, add the key to your CI as a secret, and gate the build step on a tag or merge so releases run only when you cut one.
Cloud builds, managed signing and one-call Play publishing for Expo & React Native.
Start free