Closed JeroenSchrader closed 8 months ago
Yep, this was me that caused this. See https://github.com/expo/expo/pull/26839 and https://github.com/expo/expo/pull/26901 for full context, but the gist is that the existing implementation of "fingerprintExperimental" was buggy (produced incorrect and inconsistent hashes) so we're fixing it. Rather than introduce another new "experimental" policy and then remove this one, we decided that since it was experimental to just fix it in place for the next SDK. https://github.com/expo/expo/pull/26901#pullrequestreview-1878628463
The main issue is that it is used in eas-cli (which isn't specific to any particular SDK version) so the changes to support the updated policy needed to be made there.
If you need to keep using the old implementation of the policy, I think the best solution is to stay on version 7.2.0 of eas-cli
for now until SDK 51 comes out with the fixed policy (and hopefully renamed to just "fingerprint"). Sorry for the thrash. If absolutely needed we may be able to add the previous version back under a different name, but due to its experimental nature we can't make any guarantees about using it in a project.
Reverting to eas-cli@7.2.0
works indeed, thanks! Will upgrade once SDK 51 comes out
Summary
I don't know why this error occurs and what caused it. I have successfully submitted an update (the initial update) using this command before. Even going back to the branch that I've successfully submitted an update on, it still gives me that error.
Anyone knows what causes this issue? I haven't seen it documented anywhere and I don't know what to do.
I use
"expo-updates": "~0.24.11"
I use the
fingerprintExperimental
runtimeVersion policy in myapp.config.ts
The command I run:
ENVIRONMENT=PRODUCTION eas update -p all --branch production
Output:
What platform(s) does this occur on?
Android, iOS
SDK Version
50
Environment
Minimal reproducible example
-