Open giorgiofellipe opened 3 weeks ago
szdziedzic
commented
3 weeks ago Also, I don't see the diff on logs (added on https://github.com/expo/eas-cli/pull/2422).
It seems to be a mistake on our end because the local build plugin wasn't bumped when releasing https://github.com/expo/eas-cli/pull/2422 so diffs weren't shown for local builds in 10.1.0. I bumped it and just released 10.1.1 so it should be fixed in this version.
Let's see if diff logs can help here.
giorgiofellipe
commented
3 weeks ago @szdziedzic Ok, now I see it generating a consistent hash on every run.
But I still see a mismatch, here is the diff:
[CONFIGURE_EXPO_UPDATES] Runtime version mismatch
[CONFIGURE_EXPO_UPDATES] Runtime version on your local machine: 441454b361d9ac0cae405a637d0f26bb320b18a5
[CONFIGURE_EXPO_UPDATES] Runtime version calculated on EAS: 8ab52d3a46a5b23560e594ed3fca27053a51c1c8
[CONFIGURE_EXPO_UPDATES] Difference between local and EAS fingerprints:
[CONFIGURE_EXPO_UPDATES] [
{
"op": "added",
"source": {
"type": "dir",
"filePath": "ios",
"reasons": [
"bareNativeDir"
],
"hash": null
}
},
{
"op": "changed",
"source": {
"type": "contents",
"id": "packageJson:scripts",
"contents": {
"start": "expo start",
"reset-project": "node ./scripts/reset-project.js",
"android": "expo run:android",
"ios": "expo run:ios",
"web": "expo start --web",
"test": "jest --watchAll",
"lint": "expo lint"
},
"reasons": [
"packageJson:scripts"
],
"hash": "b7dc37dfd93bfd47ef5d827587ed32f8fa796932"
}
}
]P.S.: I can confirm after replacing my scripts by the content above it has been fixed on the demo repository. Should scripts section of package.json be ignored by fingerprint?
giorgiofellipe
commented
3 weeks ago However, I still see a lot of diffs on my main project (which is in a Turbo monorepo and using pnpm).
[CONFIGURE_EXPO_UPDATES] Runtime version mismatch
[CONFIGURE_EXPO_UPDATES] Runtime version on your local machine: 92f73ae9ab9a4ae9cffb56bdb9d9d6cf6eb3418a
[CONFIGURE_EXPO_UPDATES] Runtime version calculated on EAS: 1bfe1f3b4df2a2900baa63dab0e8ae9059772f2c
[CONFIGURE_EXPO_UPDATES] Difference between local and EAS fingerprints:
[CONFIGURE_EXPO_UPDATES] [
{
"op": "changed",
"source": {
"type": "dir",
"filePath": "../../node_modules/.pnpm/expo-dev-launcher@4.0.20_expo@51.0.13/node_modules/expo-dev-launcher",
"reasons": [
"expoAutolinkingIos",
"expoConfigPlugins",
"expoConfigPlugins"
],
"hash": "30e6bef6aca813b3ac79facfc31c0e9ee8d80149"
}
},
{
"op": "changed",
"source": {
"type": "dir",
"filePath": "../../node_modules/.pnpm/expo-dev-menu@5.0.15_expo@51.0.13/node_modules/expo-dev-menu",
"reasons": [
"expoAutolinkingIos",
"expoConfigPlugins",
"expoConfigPlugins"
],
"hash": "0bb6fe06a492af6752d95e4f7237a06ca7845c38"
}
},
{
"op": "changed",
"source": {
"type": "dir",
"filePath": "../../node_modules/.pnpm/expo@51.0.13_@babel+core@7.24.7/node_modules/expo",
"reasons": [
"expoAutolinkingIos",
"expoConfigPlugins",
"expoConfigPlugins"
],
"hash": "9e0d4587c887ca968fd8db1a3331483727f9a71e"
}
},
{
"op": "added",
"source": {
"type": "dir",
"filePath": "ios",
"reasons": [
"bareNativeDir"
],
"hash": null
}
},
{
"op": "changed",
"source": {
"type": "dir",
"filePath": "node_modules/@react-native-async-storage/async-storage",
"reasons": [
"bareRncliAutolinking"
],
"hash": "b81e26351885b69d10a2d03be3b9fbdb8a4a8802"
}
},
{
"op": "changed",
"source": {
"type": "dir",
"filePath": "node_modules/@sentry/react-native",
"reasons": [
"bareRncliAutolinking"
],
"hash": "b1a175225d96faf64eeb4f78e94e484e60a0db91"
}
},
{
"op": "changed",
"source": {
"type": "dir",
"filePath": "node_modules/expo",
"reasons": [
"bareRncliAutolinking"
],
"hash": "1eb3236b60458f87f899103a25c6e3bb7183487a"
}
},
{
"op": "changed",
"source": {
"type": "dir",
"filePath": "node_modules/react-native-clarity",
"reasons": [
"bareRncliAutolinking"
],
"hash": "5f629126158efc21c662cb36de265c6735ef7c06"
}
},
{
"op": "changed",
"source": {
"type": "dir",
"filePath": "node_modules/react-native-gesture-handler",
"reasons": [
"bareRncliAutolinking"
],
"hash": "7bde148b0c39f40f11e71b347d8bec798e9151da"
}
},
{
"op": "changed",
"source": {
"type": "dir",
"filePath": "node_modules/react-native-reanimated",
"reasons": [
"bareRncliAutolinking"
],
"hash": "053298906628de8e99408874d493894e4b6782c8"
}
},
{
"op": "changed",
"source": {
"type": "dir",
"filePath": "node_modules/react-native-safe-area-context",
"reasons": [
"bareRncliAutolinking"
],
"hash": "dc9e723fea6fd25207fe4bb2c03b235ed0eba37a"
}
},
{
"op": "changed",
"source": {
"type": "dir",
"filePath": "node_modules/react-native-screens",
"reasons": [
"bareRncliAutolinking"
],
"hash": "be06c525ee1f1c57216f2f63bf491a71b2792b4f"
}
},
{
"op": "changed",
"source": {
"type": "dir",
"filePath": "node_modules/react-native-svg",
"reasons": [
"bareRncliAutolinking"
],
"hash": "deec6c89a6749857351383ad8f93956ecd33e216"
}
},
{
"op": "changed",
"source": {
"type": "dir",
"filePath": "node_modules/react-native-webview",
"reasons": [
"bareRncliAutolinking"
],
"hash": "12e0e344f6e466321e025e23df0a9cf3387cdf37"
}
}
]
kadikraman
commented
3 weeks ago @szdziedzic Ok, now I see it generating a consistent hash on every run.
But I still see a mismatch, here is the diff:
[CONFIGURE_EXPO_UPDATES] Runtime version mismatch [CONFIGURE_EXPO_UPDATES] Runtime version on your local machine: 441454b361d9ac0cae405a637d0f26bb320b18a5 [CONFIGURE_EXPO_UPDATES] Runtime version calculated on EAS: 8ab52d3a46a5b23560e594ed3fca27053a51c1c8 [CONFIGURE_EXPO_UPDATES] Difference between local and EAS fingerprints: [CONFIGURE_EXPO_UPDATES] [ { "op": "added", "source": { "type": "dir", "filePath": "ios", "reasons": [ "bareNativeDir" ], "hash": null } }, { "op": "changed", "source": { "type": "contents", "id": "packageJson:scripts", "contents": { "start": "expo start", "reset-project": "node ./scripts/reset-project.js", "android": "expo run:android", "ios": "expo run:ios", "web": "expo start --web", "test": "jest --watchAll", "lint": "expo lint" }, "reasons": [ "packageJson:scripts" ], "hash": "b7dc37dfd93bfd47ef5d827587ed32f8fa796932" } } ]P.S.: I can confirm after replacing my scripts by the content above it has been fixed on the demo repository. Should scripts section of package.json be ignored by fingerprint?
@giorgiofellipe there should have been a fix for this recently, publihsed in expo-fingerprint@0.10.0 - could you try upgrading to 0.10.0 if you're on a lower version currently?
giorgiofellipe
commented
3 weeks ago @kadikraman I'm using this very version actually.
"@expo/fingerprint": "^0.10.0",
Kudo
commented
2 weeks ago https://github.com/expo/expo/pull/30344 should fix the issue of the demo repo. for turborepo and pnpm, it looks like a different issue. would you mind to share a repro for turborepo/pnpm setup?
giorgiofellipe
commented
2 weeks ago @Kudo
Repository: https://github.com/giorgiofellipe/monorepo-expo-issue
Expo env info:
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
npmGlobalPackages:
eas-cli: 10.1.1
Expo Workflow: managedA curious thing is that when I run pnpm dlx expo-doctor it says it is everything alright, when I run eas build I have this:
[RUN_EXPO_DOCTOR] Running 12 checks on your project...
[RUN_EXPO_DOCTOR] ✔ Check Expo config for common issues
[RUN_EXPO_DOCTOR] ✔ Check package.json for common issues
[RUN_EXPO_DOCTOR] ✔ Check native tooling versions
[RUN_EXPO_DOCTOR] ✔ Check dependencies for packages that should not be installed directly
[RUN_EXPO_DOCTOR] ✔ Check for common project setup issues
[RUN_EXPO_DOCTOR] ✖ Check for issues with metro config
[RUN_EXPO_DOCTOR] Unexpected error while running 'Check for issues with metro config' check:
[RUN_EXPO_DOCTOR] Error: The required package `expo-asset` cannot be found
[RUN_EXPO_DOCTOR] ✔ Check npm/ yarn versions
[RUN_EXPO_DOCTOR] ✔ Check that packages match versions required by installed Expo SDK
[RUN_EXPO_DOCTOR] ✔ Check Expo config (app.json/ app.config.js) schema
[RUN_EXPO_DOCTOR] ✔ Check for legacy global CLI installed locally
[RUN_EXPO_DOCTOR] ✔ Check that native modules do not use incompatible support packages
[RUN_EXPO_DOCTOR] ✔ Check that native modules use compatible support package versions for installed Expo SDK
[RUN_EXPO_DOCTOR] One or more checks failed, indicating possible issues with the project.
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 #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.