Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

eas update is using cache env vars #2847

Open
hesscbjr opened this issue Jan 30, 2025 · 2 comments
Open

eas update is using cache env vars #2847

hesscbjr opened this issue Jan 30, 2025 · 2 comments
Assignees
Labels
needs review Issue is ready to be reviewed by a maintainer

Comments

@hesscbjr
Copy link

hesscbjr commented Jan 30, 2025

Build/Submit details page URL

No response

Summary

I have an expo project that is bare and uses EAS update. We have an env var called EXPO_PUBLIC_UPDATE_VERSION that we use to track the versioning of updates in any bug reports.

When I push an update, it does not always receive this value correctly. After some debugging I found that if I run npx expo start -c and then eas update the EXPO_PUBLIC_UPDATE_VERSION is updated correctly when the app receives the update.

This shouldn't be the case, the update SHOULD push the current values in .env, not any cached values in the bundler.

Managed or bare?

Bare

Environment

expo-env-info 1.2.2 environment info:
System:
OS: macOS 15.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.20.4 - ~/.nvm/versions/node/v18.20.4/bin/node
Yarn: 1.22.22 - ~/.yarn/bin/yarn
npm: 10.7.0 - ~/.nvm/versions/node/v18.20.4/bin/npm
Watchman: 2024.12.02.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.16.1 - /Users/*******/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms: DriverKit 24.2, iOS 18.2, macOS 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2
Android SDK:
API Levels: 30, 33, 34
Build Tools: 30.0.3, 33.0.0, 34.0.0
System Images: android-30 | Google APIs ARM 64 v8a, android-31 | Google APIs ARM 64 v8a, android-34 | Google APIs ARM 64 v8a
IDEs:
Android Studio: 2022.3 AI-223.8836.35.2231.11090377
Xcode: 16.2/16C5032a - /usr/bin/xcodebuild
npmPackages:
expo: ~51.0.39 => 51.0.39
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.75.4 => 0.75.4
npmGlobalPackages:
eas-cli: 12.6.2
expo-cli: 6.3.10
Expo Workflow: bare

Error output

No response

Reproducible demo or steps to reproduce from a blank project

Create an environment variable with EXPO_PUBLIC prefix that is an int.

Make a build

Send and receive the update on device

Do this a few times and verify the value after receiving the update

This can be fix by running npx expo start -c before eas update

@hesscbjr hesscbjr added the needs review Issue is ready to be reviewed by a maintainer label Jan 30, 2025
@brentvatne
Copy link
Member

@byCedric / @EvanBacon - could npx expo export not be clearing metro cache?

@hesscbjr
Copy link
Author

hesscbjr commented Feb 2, 2025

Do I need to run npx expo export separately? Or is that called when I run npx expo update?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs review Issue is ready to be reviewed by a maintainer
Projects
None yet
Development

No branches or pull requests

3 participants