You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have 2 env files
.env.development and .env.production
and building and starting (debug) are working fine. The problem is with eas update.
If I have a dev build, and push a update to dev channel, it subscribes with the production .env
Build/Submit details page URL
No response
Summary
I have 2 env files
.env.development and .env.production
and building and starting (debug) are working fine. The problem is with eas update.
If I have a dev build, and push a update to dev channel, it subscribes with the production .env
Managed or bare?
Managed
Environment
expo-env-info 1.2.0 environment info:
System:
OS: macOS 14.3.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.18.0 - /usr/local/bin/node
Yarn: 1.22.21 - /usr/local/bin/yarn
npm: 9.8.1 - /usr/local/bin/npm
Managers:
CocoaPods: 1.14.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.2, iOS 17.2, macOS 14.2, tvOS 17.2, visionOS 1.0, watchOS 10.2
IDEs:
Android Studio: 2023.1 AI-231.9392.1.2311.11076708
Xcode: 15.2/15C500b - /usr/bin/xcodebuild
npmPackages:
expo: ^49.0.0 => 49.0.22
react: 18.2.0 => 18.2.0
react-native: 0.72.10 => 0.72.10
npmGlobalPackages:
eas-cli: 7.3.0
Expo Workflow: managed
Error output
No response
Reproducible demo or steps to reproduce from a blank project
1 - Create 2 .env files
2 - Use expo 49
3 - Build a dev build
4 - Update the dev build with eas update
The text was updated successfully, but these errors were encountered: