eas env:create failing

[giorgiofellipe]

Build/Submit details page URL

No response

Summary

Out of nowhere our pipeline started failing to update env vars on EAS. It's been working for months...

Command:
eas env:create development --name "EXPO_PUBLIC_BACKEND_URL" --value "VALUE" --visibility plaintext --force --non-interactive --scope project

Managed or bare?

managed

Environment

expo-env-info 2.0.7 environment info:
System:
OS: macOS 15.1.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.7.0 - ~/.local/state/fnm_multishells/20687_1758896353877/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 10.8.2 - ~/.local/state/fnm_multishells/20687_1758896353877/bin/npm
Watchman: 2025.03.10.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.16.2 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 24.1, iOS 18.1, macOS 15.1, tvOS 18.1, visionOS 2.1, watchOS 11.1
Android SDK:
API Levels: 26, 29, 30, 31, 32, 33, 34, 35
Build Tools: 29.0.2, 29.0.3, 30.0.2, 30.0.3, 31.0.0, 32.0.0, 33.0.0, 33.0.1, 33.0.2, 34.0.0, 35.0.0
System Images: android-30 | Google APIs ARM 64 v8a, android-33 | Google APIs ARM 64 v8a, android-33 | Google APIs Intel x86_64 Atom, android-33 | Google Play ARM 64 v8a, android-34 | Google APIs ARM 64 v8a
IDEs:
Android Studio: 2024.2 AI-242.23726.103.2422.13103373
Xcode: 16.1/16B40 - /usr/bin/xcodebuild
npmPackages:
babel-preset-expo: ^13.0.0 => 13.2.4
expo: ~53.0.22 => 53.0.23
expo-router: ^5.1.5 => 5.1.7
expo-updates: ~0.28.17 => 0.28.17
react: ^19.0.0 => 19.0.0
react-dom: ^19.0.0 => 19.0.0
react-native: 0.79.6 => 0.79.6
react-native-web: ~0.20.0 => 0.20.0
Expo Workflow: bare

Error output

This project already has an environment variable named "EXPO_PUBLIC_BACKEND_URL" in the following environments: development. Choose another name or edit the existing variable.
Request ID: ad771bf3-6c38-4384-ad8f-70e8bcba79d7

Reproducible demo or steps to reproduce from a blank project

Run twice: eas env:create development --name "EXPO_PUBLIC_BACKEND_URL" --value "VALUE" --visibility plaintext --force --non-interactive --scope project

[giorgiofellipe]

Please also consider merging asap #3135

[yonitou]

Same error

[kadikraman]

Hi @giorgiofellipe - could you try using the latest eas-cli (version 16.20.2) and including the --environment flag?

Edit: don't do this - real fix incoming.

[giorgiofellipe]

Applied a workaround by using update for existing variables, which is totally not ideal as these command are extremely slow (that's why I'm begging to get env:push --force merged asap)...
Now eas-cli version 16.20.2 introduced another breaking change 🤦🏻

As you mentioned @kadikraman, it now requires --environment param, before it was the first arg by default = breaking change.
Also, even passing the --environment and --non-interactive options it's asking to select the variable I want to update, see:

Too many damn breaking changes

[kadikraman]

Thanks for sharing an example where it's not working as expected - will investigate.

[giorgiofellipe]

@kadikraman The command env:create with --environment and --force seems to be working as expected. But the above regarding env:update is still true tho.
Also the env:get is not respecting the pattern:

eas env:get development --variable-name "EXPO_PUBLIC_BACKEND_URL" --non-interactive
Invalid environment. Use one of 'production', 'preview', or 'development'.
    Error: env:get command failed.

eas env:get --environment development --variable-name "EXPO_PUBLIC_BACKEND_URL" --non-interactive
Unexpected argument: development
See more help with --help
    Error: env:get command failed.

The only one that works is: eas env:get --variable-environment development --variable-name "EXPO_PUBLIC_BACKEND_URL" --non-interactive.
There is absolutely no pattern for the params across env commands...

Please check the outdated --help that leads to errors as well.

[kadikraman]

This should be resolved now in eas-cli@16.20.3 - please let me know if you encounter any other issues.