Expo EAS
Expo Build (Expo Build (EAS Build) Build) builds on Expo servers. Keep doing that, and send the internal distribution builds to AppForShare, from GitHub Actions or from an Expo Workflows job for your install page, channels, tester groups and the store readiness check. There are four ways: Connect Expo (a webhook, no CI step, Pro and Team), a custom job in Expo Workflows, the CLI on your own computer, or GitHub Actions. With no CI at all, Connect Expo (Pro and Team) receives each finished EAS build through an EAS build webhook instead.
1. Add your token
Create an API token under Dashboard, Settings, API tokens (Pro and Team). For Connect Expo nothing is stored anywhere: the webhook secret goes to Expo with eas webhook:create. For Expo Workflows, add APPFORSHARE_TOKEN as an Expo environment variable with secret visibility. For other CI, store EXPO_TOKEN (from expo.dev, Access tokens) and APPFORSHARE_TOKEN as secrets. The CLI reads it from the APPFORSHARE_TOKEN environment variable.
2. eas.json profile
Internal distribution makes an APK for Android and an ad hoc build for iOS. Store builds (distribution: store) and simulator builds cannot install from a link, so they are skipped.
{
"build": {
"preview": {
"distribution": "internal",
"android": { "buildType": "apk" }
}
}
}3. Connect Expo: a webhook, no CI step (Pro and Team)
In AppForShare open the project, Testing, Connect Expo, and press Make a webhook address (or run appforshare eas connect --project <id>). Run the command it shows once in your Expo project folder. From then on, every finished internal build arrives on its own: AppForShare checks the expo-signature header, fetches the file from Expo, writes the release notes from the build message or commit, and puts it in the channel you mapped to its build profile, for example preview=Beta. Store and simulator builds are skipped with a note, failed builds go to your build.failed webhooks, and the optional SUBMIT webhook adds EAS Submit results to the release timeline.
# printed by AppForShare, with your own address and secret
eas webhook:create --event BUILD --url "https://appforshare.io/api/hooks/eas/<token>" --secret "<secret>"
# optional: EAS Submit results on the release page timeline
eas webhook:create --event SUBMIT --url "https://appforshare.io/api/hooks/eas/<token>" --secret "<secret>"
# from the CLI, with build profiles mapped to channels
npx --yes appforshare eas connect --project 42 --profile preview=Beta4. Expo Workflows: .eas/workflows/share.yml
A custom job after the build job: eas/download_build fetches the file and the AppForShare CLI uploads it. Add APPFORSHARE_TOKEN as an Expo environment variable (secret visibility) in the environment the job uses; the job below sets preview. The share job is a short Linux job, so it uses a little of your Workflows minutes (Free plans include 60 a month as listed on November 4, 2026).
name: Share preview builds
on:
push:
branches: ['main']
defaults:
tools:
node: '22'
jobs:
build_ios:
type: build
params:
platform: ios
profile: preview
share:
needs: [build_ios]
environment: preview
steps:
- uses: eas/download_build
id: download_build
with:
build_id: ${{ needs.build_ios.outputs.build_id }}
- run: npx --yes appforshare upload "${{ steps.download_build.outputs.artifact_path }}" --channel beta5. CLI on your computer
The CLI runs eas build:view --json or eas build:list --json on the same machine, downloads the build and fills the release notes from it. Your EXPO_TOKEN or eas login never leaves the machine. init in an Expo project reads the profiles in eas.json and saves the one --eas-latest uses.
# one build by its Expo id
npx --yes appforshare upload --eas 147a3212-49fd-446f-b4e3-a6519acf264a --channel beta
# the newest finished build of a profile (both platforms, or one with --platform)
npx --yes appforshare upload --eas-latest --profile preview --platform ios
# iPhones registered with Expo, into AppForShare devices
eas device:list --json | npx --yes appforshare devices import -6. GitHub Actions job
eas build --json --wait prints the finished build, including artifacts.buildUrl.
- uses: actions/setup-node@v4
with:
node-version: 22
- run: npm ci
- name: Build on EAS
run: npx --yes eas-cli build --platform android --profile preview --non-interactive --wait --json > eas-build.json
env:
EXPO_TOKEN: ${{ secrets.EXPO_TOKEN }}
- name: Share with testers
run: |
curl -sL "$(jq -r '.[0].artifacts.buildUrl' eas-build.json)" -o app.apk
npx --yes appforshare upload app.apk --notes "${{ github.event.head_commit.message }}" --channel beta
env:
APPFORSHARE_TOKEN: ${{ secrets.APPFORSHARE_TOKEN }}7. Shorter: let the CLI fetch the EAS build
appforshare upload --eas asks eas-cli on the same machine for the build, downloads it and fills the release notes. EXPO_TOKEN stays on the runner.
- name: Share the newest preview build
run: npx --yes appforshare upload --eas-latest --profile preview --platform android --channel beta
env:
EXPO_TOKEN: ${{ secrets.EXPO_TOKEN }}
APPFORSHARE_TOKEN: ${{ secrets.APPFORSHARE_TOKEN }}8. Expo Workflows job (.eas/workflows)
Add APPFORSHARE_TOKEN as a secret environment variable in your Expo project. A custom job downloads the build with eas/download_build and uploads it. It runs on your Expo Workflows minutes.
jobs:
build_preview_ios:
type: build
params:
platform: ios
profile: preview
share:
needs: [build_preview_ios]
steps:
- uses: eas/download_build
id: download_build
with:
build_id: ${{ needs.build_preview_ios.outputs.build_id }}
- run: npx --yes appforshare upload "${{ steps.download_build.outputs.artifact_path }}" --channel betaGood to know
- For iOS use --platform ios and save the file as app.ipa. Ad hoc builds only install on registered iPhones; AppForShare can collect UDIDs from testers and register them on your Apple account.
- Devices go both ways: eas device:list --json into appforshare devices import, or register iPhones on Apple with AppForShare, then run eas device:create and import them from your Apple Developer Portal, so the next EAS build includes them.
- Connect Expo needs CLI 1.19.0 or later for eas connect, upload --eas and devices import from stdin.
- Add --channel beta to keep one stable link for testers, and --fail-on blocked to stop the pipeline when the store readiness check finds a blocker (exit code 2; the build stays uploaded).
- The command prints the install link. Add --json for url, slug, version and channel as JSON. All options are on Upload from CI.
Use AppForShare with Expo EAS: Connect Expo, iPhone devices, update channels and store steps
Questions
- Why not just send the EAS link?
- You can. AppForShare adds a branded install page with a QR code, channels with a link that never changes, install analytics, tester groups, a store readiness check and a test plan per build.
- Does Connect Expo need a CI step?
- No. Run eas webhook:create once with the address and secret AppForShare shows. Expo then calls AppForShare when a build finishes, and AppForShare fetches the file from Expo. Connect Expo is part of Pro and Team.
- What happens to store builds?
- Builds with distribution: store and iOS simulator builds cannot install from a link, so Connect Expo skips them and says so on the project. Use a profile with distribution: internal for testers.
- Can I build an .aab with EAS and still share it?
- Yes. Upload the .aab and AppForShare turns it into one APK for testers.
- Can I skip the CI step?
- Yes, on Pro and Team. Connect Expo gives your project an EAS build webhook address and secret; run eas webhook:create --event BUILD once and each finished internal build is shared without any pipeline.
Other CI systems
GitHub Actions and FastlaneCircleCIGitLab CIBitbucket PipelinesJenkinsAzure PipelinesXcode CloudCodemagicBitrise