> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revyl.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Expo

> Connect EAS to Revyl and auto-import every new build

Connect your Expo project once and every new EAS build lands in Revyl automatically. No uploads, no manual steps. Every passing build is ready to test the moment EAS finishes it.

## How It Works

1. You give Revyl an **Expo access token** (stored encrypted)
2. You link an **EAS project** to one or more Revyl apps (one Android, one iOS, or both)
3. Revyl **automatically registers a webhook** on your EAS project using the token
4. EAS fires the webhook to Revyl on every completed build
5. Revyl filters the build, downloads the artifact, and creates a new Build inside the linked app

Builds auto-synced this way get tagged with `source: expo` and an auto-generated version like `expo-1.2.0-ios-a1b2c3d4`. Native changes get a `-native` suffix so you can tell at a glance what changed.

## Requirements

<Steps>
  <Step title="Expo access token">
    Create a **Robot User access token** at [expo.dev/settings/access-tokens](https://expo.dev/settings/access-tokens). Robot users are the [recommended pattern](https://docs.expo.dev/accounts/programmatic-access/) for CI/integration tokens. Personal tokens work but aren't ideal.

    The Robot User needs **Developer role or higher** on the EAS project. Read-only tokens can't create webhooks and will fail at registration.
  </Step>

  <Step title="EAS project ID">
    Grab your project's UUID from the Expo Dashboard or `app.json`. It must be a valid UUID. The human-readable `@owner/slug` form is not accepted.
  </Step>

  <Step title="Simulator/emulator builds">
    Revyl runs on cloud simulators and emulators — your EAS profile must produce compatible binaries. See [Artifact Requirements](/builds/artifact-requirements) for the full rules.

    * **iOS**: `"simulator": true` on the profile in `eas.json`
    * **Android**: a debuggable `.apk` (not `.aab`) whose native libraries include `x86_64` or `arm64-v8a`
  </Step>
</Steps>

## Setup

### 1. Create an Expo Robot User Token

1. Sign in to [expo.dev](https://expo.dev)
2. Go to [Access Tokens](https://expo.dev/settings/access-tokens)
3. Click **Create Token**
4. Give it a descriptive name like `revyl-auto-sync`
5. Make sure the Robot has **Developer role or higher** on the EAS project
6. Copy the token immediately (it won't be shown again)

### 2. Configure Expo in Revyl

1. In Revyl, go to **Integrations > Expo**
2. Paste your **Robot User access token** and save
3. Click **Add EAS Project**
4. Enter the **EAS Project ID** (UUID), a display name, and pick which Revyl Android and/or iOS apps it maps to
5. Enable **Auto-sync** and save

Revyl registers the webhook on your EAS project in the background. Nothing else to do.

### Alternative: From the App Creation Flow

When creating an app, click **Connect to Expo** instead of uploading a file. The flow prompts for the token if you don't have one, then shows a project picker. Revyl auto-selects the latest compatible build (non-production, non-expired, matching platform) and imports it as your first build. Future builds sync automatically.

## What Gets Synced

On each EAS `BUILD` event with `status=finished`, Revyl:

1. Verifies the webhook signature (HMAC-SHA1 `expo-signature`)
2. Matches the build to an org via the signature
3. Filters out:
   * **Production profiles** (filtered by name)
   * **Expired artifact URLs**
   * **iOS builds without `"simulator": true`**
   * **`.aab` Android builds**
4. Downloads the artifact using your Expo token
5. Creates a new build in the linked Revyl app, comparing its `fingerprintHash` to the previous build to detect native changes

## Managing the Integration

* **Update the token**: go to **Integrations > Expo**, paste a new token, save. Existing builds stay; future syncs use the new token.
* **Disconnect**: clear the token field and save. Revyl stops syncing and removes the webhook from EAS. Existing builds remain and can still be run against.
* **Remap a project**: connecting an EAS project to a new app reassigns the platform binding. The old app stops auto-syncing.

## Gotchas

* **One EAS project maps to one app per platform.** Remapping reassigns the binding.
* **Production profiles are filtered on purpose.** Revyl doesn't import production builds via auto-sync. Upload them manually if you need to test production artifacts.
* **If webhook registration fails**, the Robot User probably has read-only access. The Robot needs Developer role or higher on the EAS project.
* **If builds aren't showing up**: check `simulator: true` is set on your iOS profile, that you're building `.apk` not `.aab` on Android, and that the artifact URL hasn't expired.
* **Auto-sync stops if the token is removed.** Disabling auto-sync also deletes the webhook from EAS automatically.

## Recommended `eas.json`

See [EAS JSON Setup](/builds/frameworks/expo#eas-json-setup) for more info on the EAS profiles that should be configured

## Related

* [Apps](/builds/index): create apps and manage builds
* [Expo Auto Sync](/builds/expo-sync): conceptual overview