Expo Integration

​

Overview

• Automatic build imports - Pull builds directly from EAS
• Version synchronization - New EAS builds appear in Revyl automatically
• Streamlined workflow - Build once in Expo, test immediately in Revyl
• Support for both iOS and Android - Import both platform builds

​

Prerequisites

1. An Expo account - Sign up at expo.dev
2. An Expo project with EAS Build configured
3. Robot User access - Create a programmatic access token
4. At least one EAS build - Build your app using eas build

​

Setup Guide

​

Step 1: Create an Expo Robot User

1. Log in to Expo
   • Go to expo.dev and sign in
2. Create a Robot User
   • Navigate to your account settings
   • Go to Access Tokens or Robot Users
   • Click Create Robot User
   • Give it a descriptive name: revyl-build-access
3. Generate Access Token
   • Select the robot user you just created
   • Click Create Token
   • Set permissions: Read access to builds (minimum required)
   • Copy the generated token immediately (it won’t be shown again!)

​

Step 2: Configure Expo in Revyl

1. Navigate to Integrations
   • In Revyl, click Integrations in the sidebar
   • Click the Expo Settings tab

2. Paste the Access Token
   • Find the Expo Robot User Access Token field
   • Paste the token you copied from Expo
   • Click the eye icon to verify it’s correct
3. Save Changes
   • Click Save Changes
   • Revyl will verify the token by making a test API call to Expo
4. Success!
   • If valid, you’ll see a success message
   • Revyl can now access your Expo builds

​

Step 3: Add an Expo Project

1. In the Expo Projects section, click + Add Project
2. Enter your Expo project slug (e.g., @your-username/my-app)
3. Click Add
4. The project appears in the list, enabling build imports

​

Step 4: Import Builds from the Builds Page

1. Go to Builds in the sidebar
2. Select any build from the list
3. Click Upload from Expo button (top right of build detail panel)

4. In the modal, select your Expo project from the dropdown

5. Click Fetch to load available EAS builds

6. Click a build to select it
7. Click Import Build to add it as a new version

​

How It Works

​

Build Synchronization

1. You run eas build in your Expo project
2. EAS builds your app (iOS/Android)
3. Revyl detects the new build (within ~5 minutes)
4. Build appears in Revyl under the Builds page
5. You can now create tests using that build

​

Build Matching

• App identifier - Bundle ID (iOS) or Package Name (Android)
• Version - App version string
• Build number - Build number from app.json or app.config.js

​

Supported Build Types

• ✅ iOS builds - zipped .app files from EAS
• ✅ Android builds - .apk files from EAS
• ✅ Development builds - With Expo Dev Client
• ✅ Production builds - Release builds for testing before distribution

​

Managing Expo Integration

​

Viewing Connection Status

1. Go to Integrations → Expo Settings
2. If a token is configured, you’ll see:
   • The token field is filled (hidden by default - click eye icon to reveal)
   • Save Changes button is disabled (no changes)
3. If disconnected:
   • The field is empty
   • You’ll see the “Enter Expo access token” placeholder

​

Updating the Token

1. Generate a new token in Expo (follow Step 1 above)
2. Go to Integrations → Expo Settings
3. Clear the existing token and paste the new one
4. Click Save Changes

​

Disconnecting Expo

1. Go to Integrations → Expo Settings
2. Clear the Expo Robot User Access Token field
3. Click Save Changes
4. Revyl will no longer sync new builds from Expo

​

Build Import Workflow

​

Typical Expo + Revyl Workflow

1. Develop your app
   Copy

   cd my-expo-app
   npm install
   
2. Build with EAS
   Copy

   eas build --platform android --profile preview
   
3. Wait for build to complete
   • Monitor progress in the terminal or at expo.dev/builds
4. Build appears in Revyl automatically
   • Go to Revyl Builds page
   • See the new build listed
   • Or create a test and select it from the build dropdown
5. Create and run tests
   • Use the imported build in your tests
   • No need to manually download/upload!

​

Best Practices

​

Token Security

• Use Robot Users, not personal tokens - Avoids tying builds to individual accounts
• Don’t commit tokens to Git - Store in environment variables or secrets
• Rotate tokens periodically - Generate new tokens every 6-12 months
• Revoke tokens you’re not using - Clean up old tokens in Expo settings

​

Build Profiles

// eas.json
{
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal"
    },
    "preview": {
      "distribution": "internal",
      "android": { "buildType": "apk" }
    },
    "production": {
      "distribution": "store"
    }
  }
}

eas build --platform android --profile preview

​

Versioning

{
  "expo": {
    "version": "1.2.3",
    "android": {
      "versionCode": 10203
    },
    "ios": {
      "buildNumber": "1.2.3"
    }
  }
}

​

Hot Reload with Expo

​

Quick Setup

1. Build a development client with expo-dev-client:
   Copy

   npx eas build --profile development --platform ios
   
2. Upload to Revyl as a build:
   Copy

   revyl build upload --file <path-to-build> --name "ios-dev-client"
   
3. Configure hot reload:
   Copy

   revyl init --hotreload
   
4. Run tests with hot reload:
   Copy

   revyl dev test run login-flow
   

​

Next Steps

• Upload builds manually →
• Create a test →
• Set up GitHub integration →
• Automate with CI/CD →