Always generating different fingerprints for my builds, also not showing the fingerprint diff #2448
Assignees
Labels
Comments
giorgiofellipe
added
the
needs review
It seems to be a mistake on our end because the local build plugin wasn't bumped when releasing #2422 so diffs weren't shown for local builds in Let's see if diff logs can help here. |
|
@szdziedzic But I still see a mismatch, here is the diff: P.S.: I can confirm after replacing my scripts by the content above it has been fixed on the demo repository. |
|
However, I still see a lot of diffs on my main project (which is in a Turbo monorepo and using pnpm). |
@giorgiofellipe there should have been a fix for this recently, publihsed in |
|
@kadikraman I'm using this very version actually. |
Merged
3 tasks
Kudo
added a commit
to expo/expo
that referenced
this issue
Jul 11, 2024
…fNotContainRun (#30344) # Why the `SourceSkips.PackageJsonAndroidAndIosScriptsIfNotContainRun` does not actually work. fixes expo/eas-cli#2448 # How - fix broken updates e2e test. this was because we have `require(/path/to/app/package.json)` that will be cached from jest tests. this pr uses `jest.resetModules()` to prevent the cache. - fix broken `SourceSkips.PackageJsonAndroidAndIosScriptsIfNotContainRun`. after prebuild, the script would be `expo run:android` or `expo run:ios`, we should also strip the script to make the source consistent before and after prebuild. (cherry picked from commit 6af77cf)
|
expo/expo#30344 should fix the issue of the demo repo. |
szdziedzic
added
eas build
needs more info
and removed
needs review
|
Repository: https://github.com/giorgiofellipe/monorepo-expo-issue Expo env info: A curious thing is that when I run And this is the fingerprint diff |
alanjhughes
pushed a commit
to expo/expo
that referenced
this issue
Jul 17, 2024
…fNotContainRun (#30344) # Why the `SourceSkips.PackageJsonAndroidAndIosScriptsIfNotContainRun` does not actually work. fixes expo/eas-cli#2448 # How - fix broken updates e2e test. this was because we have `require(/path/to/app/package.json)` that will be cached from jest tests. this pr uses `jest.resetModules()` to prevent the cache. - fix broken `SourceSkips.PackageJsonAndroidAndIosScriptsIfNotContainRun`. after prebuild, the script would be `expo run:android` or `expo run:ios`, we should also strip the script to make the source consistent before and after prebuild.
|
Does eas update generate runtime versions again, it doesn't have a |
|
The problem is eas update doesnt even use the env vars as usual, its loading them from eas.json this is so frustrating and affecting our workflows |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Build/Submit details page URL
No response
Summary
I have configured my Expo app to use fingerprint as runtime policy but I'm unable to use EAS Updates because it always generate the build with a different fingerprint
Even running locally using eas-cli v10.1.0 it's generating new fingerprint every build.
Also, I don't see the diff on logs (added on expo/expo#2422).
Managed or bare?
Managed
Environment
expo-env-info 1.2.0 environment info:
System:
OS: macOS 13.5.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.2.0 - /opt/homebrew/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 10.7.0 - /opt/homebrew/bin/npm
Managers:
CocoaPods: 1.15.2 - /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
Android SDK:
API Levels: 26, 29, 30, 31, 32, 33, 34
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
System Images: android-30 | Google APIs ARM 64 v8a, android-33 | Google APIs ARM 64 v8a, android-33 | Google Play ARM 64 v8a, android-34 | Google APIs ARM 64 v8a
IDEs:
Android Studio: 2022.3 AI-223.8836.35.2231.10671973
Xcode: 15.2/15C500b - /usr/bin/xcodebuild
npmPackages:
expo: ~51.0.18 => 51.0.18
expo-router: ~3.5.17 => 3.5.17
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.74.3 => 0.74.3
react-native-web: ~0.19.10 => 0.19.12
npmGlobalPackages:
eas-cli: 10.1.0
Expo Workflow: managed
✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check native tooling versions
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check for issues with metro config
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules use compatible support package versions for installed Expo SDK
Didn't find any issues with the project!
Error output
[CONFIGURE_EXPO_UPDATES] Runtime version from the app config evaluated on your local machine (5b9cea733cdb7a2a2a4e25163b2b6f0a8b15923b) does not match the one resolved here (047be799fde8148e8f809697fd6200c3112a2c1f).
[CONFIGURE_EXPO_UPDATES] If you're using conditional app configs, e.g. depending on an environment variable, make sure to set the variable in eas.json or configure it with EAS Secret.
Reproducible demo or steps to reproduce from a blank project
https://github.com/giorgiofellipe/fingerprint-issue-reproducible
Run
eas build --profile simulator --platform ios --non-interactive --localand you'll always see the message[CONFIGURE_EXPO_UPDATES] Runtime version from the app config evaluated on your local machine (X) does not match the one resolved here (Y)., where Y is different on every run.The text was updated successfully, but these errors were encountered: