Back to Documentation

Understanding Builds

Learn how ExpoDeploy automates your build process, from code push to artifact generation. Builds run on Expo's infrastructure and integrate seamlessly with your deployment workflow.

Automatic Build Triggers

Builds start automatically when you push code

When you push commits to a configured branch, GitHub webhooks notify ExpoDeploy, which immediately triggers an Expo EAS build. The entire process is automated - no manual intervention needed. Builds typically start within seconds of your push.

Build Profiles & Environments

Match builds to your deployment needs

Configure different build profiles per branch. Use development builds for feature testing, preview builds for internal distribution, and production builds for store releases. Each profile can have different environment variables, app configurations, and deployment targets.

Multi-Platform Support

Build for iOS, Android, or both platforms

Select which platforms to build for each branch. iOS builds produce IPA files for App Store distribution, while Android builds create AAB files for Google Play. Both platforms can build simultaneously, or you can build them separately based on your release schedule.

Real-Time Monitoring

Track build progress and access detailed logs

Monitor builds in real-time through your dashboard. See build status (queued, in-progress, completed, failed), estimated completion time, and access full build logs. Failed builds include error messages and stack traces to help you debug issues quickly.

Build Lifecycle

Here's what happens when you push code to a configured branch:

  1. 1
    Code Push - You push commits to your GitHub repository
  2. 2
    Webhook Notification - GitHub sends a webhook to ExpoDeploy within seconds
  3. 3
    Build Trigger - ExpoDeploy validates the push and triggers Expo EAS build
  4. 4
    Build Execution - Expo EAS builds your app on their cloud infrastructure (typically 10-20 minutes)
  5. 5
    Artifact Generation - Build completes and produces IPA (iOS) or AAB (Android) files
  6. 6
    Automatic Deployment - If configured, artifacts are automatically uploaded to App Store Connect or Google Play Console