eas/build custom configs can upload the embedded bundle
Introduced 2026-10-07 · score 0.90
HOW TO USE IT
For a custom build that uses `eas/build`, embedded-bundle upload is included when eligible. Add `eas/upload_embedded_bundle` only to a custom config that does not use `eas/build`; adding it alongside an enabled upload can make the second upload fail.
build:
steps:
- eas/build- eas/upload_embedded_bundle- eas/upload_embedded_bundle:
inputs:
ignore_error: trueWHY THIS HELPS
Configure a custom EAS build to upload its embedded bundle.
REQUIREMENTS AND LIMITATIONS
- Version: v24.12.0
- `eas/build` inputs: The function accepts no inputs; its build process uses the build profile in `eas.json`.
- `inputs.ignore_error`: Boolean; defaults to `false`. When `true`, logs an upload failure without failing the build. No documented mutual-exclusion rule.
- Prerequisite: Custom build YAML belongs under `.eas/build/`; configure the build profile in `eas.json` to use that config.
- Prerequisite: The upload step skips if EAS Update is not configured, or for development builds and iOS Simulator builds. It uses the build profile's `channel` and `applicationArchivePath` (or the default output path); a missing channel or app can fail the step.
- Applies to custom builds that use `eas/build`.
- Docs conflict: The card's `new_action` says to add `eas/upload_embedded_bundle` to a config using `eas/build`. Official docs say `eas/build` already uploads when enabled and warn that adding the step can trigger a failing duplicate upload. The release note is consistent with automatic upload from `eas/build`.
FIRST-PARTY EVIDENCE
- https://github.com/expo/eas-cli/releases/tag/v24.12.0
- https://docs.expo.dev/custom-builds/schema/
- https://docs.expo.dev/custom-builds/get-started/
Check the installed version and the source before using it. Entry JSON