Skip to content
Skip to content
Goodspeed

Connect EAS Build to your Goodspeed app

Cloud iOS and Android builds, OTA updates, and App Store/Play Store submission without a Mac or local build environment. Goodspeed wires EAS Build into every app that needs it at generation time, so you start with a working integration, not a blank config and a documentation tab.

WHAT GETS WIRED IN

Built into every EAS Build build

Every app Goodspeed generates with EAS Build includes these wired integrations from the first build. No manual setup required.

ItemDescriptionStrength
eas.json with three profiles: development (development client), staging (internal distribution), and production (store submission)eas.json with three profiles: development (development client), staging (internal distribution), and production (store submission)01
EAS Update channel read from EXPO_PUBLIC_RELEASE_CHANNEL env var, controlling which OTA channel the app subscribes toEAS Update channel read from EXPO_PUBLIC_RELEASE_CHANNEL env var, controlling which OTA channel the app subscribes to02
Build caching wired for the node_modules layer and native binary, reducing most JS-only builds to under two minutesBuild caching wired for the node_modules layer and native binary, reducing most JS-only builds to under two minutes03
scripts/release.mjs runs tsc --noEmit, bumps the version, triggers EAS Build, and pushes the OTA update in sequencescripts/release.mjs runs tsc --noEmit, bumps the version, triggers EAS Build, and pushes the OTA update in sequence04
app.config.js reads gas.config.ts to write app name, bundle ID, scheme, splash, and icon into the Expo config at build timeapp.config.js reads gas.config.ts to write app name, bundle ID, scheme, splash, and icon into the Expo config at build time05

Source: gas-template repository · build/deploy

REAL GENERATED CODE

A snippet from a EAS Build integration the pipeline ships

This pattern comes directly from the gas-template codebase. The studio generates EAS Build integration code like this for every app that includes it, not a placeholder you have to fill in yourself.

  1. Three-profile eas.json

    // eas.json
    {
      "build": {
        "development": {
          "developmentClient": true,
          "distribution": "internal"
        },
        "staging": {
          "distribution": "internal",
          "channel": "staging"
        },
        "production": {
          "autoIncrement": true,
          "channel": "production"
        }
      }
    }
GDaily Allergens

Today's log

Gluten
Tree nuts
Shellfish
Dairy
HomeScanLogProfile

START WITH EAS BUILD

Your EAS Build integration, generated