Equivalent functionality of secret:push causing not able to load env variable that uses custom env files #2753
Description
Build/Submit details page URL
No response
Summary
The recent changes has been a big disappointment. Broke the code and having to spend hours to get environment variables fix. Why not just let user push env file to the eas including secrets. Now I have to convert all variables to non-secret just to pass the file. If the need is that critical have a flag that allows to keep using old. Expo/EAS upgrade is the most dreading part of developer experience. Please improve it.
If I use EXPO_SENSITIVE_ as prefix will I have to change the variable all in the code or it auto removes the prefix.
Managed or bare?
Managed
Environment
expo-env-info 1.2.1 environment info:
System:
OS: Windows 11
Binaries:
Node: 20.17.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
npm: 10.8.1 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: AI-231.9392.1.2311.11076708
npmPackages:
@expo/webpack-config: ^19.0.1 => 19.0.1
expo: ^51.0.36 => 51.0.39
react: 18.3.1 => 18.3.1
react-dom: 18.3.1 => 18.3.1
react-native: 0.76.5 => 0.76.5
react-native-web: ~0.19.13 => 0.19.13
Error output
You cannot change a secret variable to a non-secret variable.
Request ID:
Error: GraphQL request failed.
Reproducible demo or steps to reproduce from a blank project
You cannot change a secret variable to a non-secret variable.
Request ID
Error: GraphQL request failed.