Over-the-air updates
LEAS 1.1 adds authenticated remote publishing to the free, self-hosted update server. Publish from your Mac or CI, test a preview channel, then promote the same JavaScript and asset bytes to production. No LEAS account or Pro subscription is required.
Install expo-updates, configure the HTTPS manifest URL, runtime and channel,
and ship one new store binary per platform. Existing binaries that point at
u.expo.dev still use Expo. Keep their EAS Update service available during migration.
Native library, SDK, permission and certificate changes require another native release.
1. Run a persistent update server
Use one shared server and persistent volume for your apps, with a unique project ID per repository. HTTPS, backups, monitoring and hosting costs belong to the operator. The Dockerfile and Railway configuration are included in the product repository. Do not run this disk-backed server on ephemeral serverless storage.
export LEAS_UPDATE_TOKEN=<secret-from-your-secret-manager> leas update:serve --port 4190 --url https://updates.example.com
/health reports liveness; /api/manifest serves manifests;
/api/assets serves exported assets. Authenticated management lives under
/api/manage/. Back up the persistent data directory, including projects/*/.leas/updates and retain old releases.
2. Configure and build each app
npm install --save-dev leas-cli@1.1.1 leas update:configure --url https://updates.example.com --project my-app
One shared service supports many repositories. Each project gets its own releases,
channels, runtime matching, assets and rollback state under /projects/my-app.
No additional server is needed. The project URL is saved in leas.json and used
automatically by publish, list, promote and rollback. The first authenticated publish creates
the project. Dynamic app configs need the printed settings applied manually.
{
"expo": {
"runtimeVersion": { "policy": "appVersion" },
"updates": {
"url": "https://updates.example.com/projects/my-app/api/manifest",
"requestHeaders": { "expo-channel-name": "production" }
}
}
}
Merge these fields with your existing config. Review your runtime policy: a matching string
is only safe when native code is actually compatible. Bump the app version for native changes
when using appVersion. LEAS does not compute fingerprint runtimes yet.
Regenerate or update existing native projects before building. LEAS skips prebuild when native directories already exist, so changing app.json alone does not update those projects. Build a preview-channel binary for testing and a production-channel binary for the store.
3. Publish from your repository
export LEAS_UPDATE_URL=https://updates.example.com/projects/my-app
# Load LEAS_UPDATE_TOKEN from a secret manager or CI secret.
leas update --channel preview --platform all --message "Fix checkout"
leas update:list --channel preview --runtime 1.0.0 --json
leas update:promote --from preview --to production --platform ios --runtime 1.0.0
leas update:promote --from preview --to production --platform android --runtime 1.0.0
--platform all exports iOS and Android separately, avoiding web export.
Channels are isolated by runtime and platform. A publish receives a new UUID; existing
release bytes are never overwritten. Promotion republishes the tested bytes with a new
release identity and time so devices can select it.
Without a URL in leas.json, LEAS_UPDATE_URL or --url, publishing and management are local only. With the URL set, list, promote and rollback operate on that server. Load the same
production environment used by the binary; LEAS does not fetch your EAS environment.
4. Roll back
leas update:rollback --channel production --platform ios --runtime 1.0.0 --to UPDATE_UUID leas update:rollback --channel production --platform android --runtime 1.0.0 --embedded
An older release is republished under a fresh identity and timestamp. Embedded rollback tells clients to return to the bundle shipped in the binary. Devices receive the instruction at their next update check; this is not an immediate push notification.
Code signing
leas update:keys npx @expo/code-signing-certificates generate-certificate \ --key-input-directory credentials/updates \ --certificate-output-directory credentials/updates
Embed the generated X.509 certificate with expo.updates.codeSigningCertificate
and metadata { "keyid": "main", "alg": "rsa-v1_5-sha256" }. Mount the private
key on your server or supply LEAS_UPDATE_PRIVATE_KEY_BASE64 through its secret
manager. The operator token and private key must never enter the client bundle.
The configured client verifies signed manifests and asset hashes. Enabling or rotating the embedded certificate needs a new runtime and native build. Validate on release devices.
For team-specific publish access, configure LEAS_UPDATE_PROJECT_TOKENS_JSON
on the server as a map from project IDs to unique tokens. Each mapped project accepts only
its mapped token; unmapped projects accept the root operator token. Store tokens in CI secrets.
Operational limits
Use one replica with persistent disk. Uploads are bounded JSON/base64 up to 100 MiB including encoding. Multi-platform operations are sequential, not atomic. There is no managed delivery, percentage rollout, automatic Sentry upload or remote environment service. Pro is the hosted dashboard, not hosted OTA delivery.
For Docker and Railway deployment, backups, acceptance checks and troubleshooting, see the OTA operations guide.