🛠️ Developer ToolsExpoci-cd

Expo EAS build fails: runtimeVersion policy not supported in bare workflow

Fresh6 months ago

Mar 14, 20260 views

Confidence Score68%

68%

Problem

Expo EAS build fails for projects in the bare workflow when app.json uses `"runtimeVersion": { "policy": "appVersion" }`. The policy-based runtime version is only supported in managed workflow projects. Bare workflow projects must set runtimeVersion to a literal string matching the version field. AI-generated app.json files and Expo documentation examples often show the policy form without this distinction.

Error Output

CommandError: runtime version policies are not supported for projects that use the "bare" workflow.

Unverified for your environment

Select your OS to check compatibility.

Your OS

OS version

Product version

1 Fix

Canonical Fix

Moderate Confidence Fix

67% confidence83% success rate7 verificationsLast verified Mar 14, 2026

Set runtimeVersion to a literal string in app.json for bare workflow

Low Risk

Policy-based runtimeVersion (e.g. {"policy": "appVersion"}) is only supported in managed Expo workflow. Bare workflow projects must use a literal string.

Trust Score

7 verifications

83% success

Change runtimeVersion in app.json to a literal string

Update app.json:

json

// ❌ Fails in bare workflow
"runtimeVersion": { "policy": "appVersion" }

// ✅ Literal string matching your version field
"version": "1.0.5",
"runtimeVersion": "1.0.5"

2
Keep runtimeVersion in sync with version
Every time you bump version in app.json, also update runtimeVersion to the same value.
3
Re-run the EAS build
Run `eas build --platform all` after the fix.

Validation

EAS build succeeds without "runtime version policies are not supported" error.

Verification Summary

Worked: 7

Partial: 3

Failed: 2

Last verified Mar 14, 2026

Environment

Product: Expo EAS Build
Environment: ci-cd

Submitted by

Alex Chen

2450 rep