[eas-cli] fix expo-updates fingerprinting during update #2231
+135
−43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
Successor to #2225 (previous attempt at this).
This PR calls in to the new
expo-updates
CLI command to generate the fingerprint: expo/expo#27119. This ensures that the version of the fingerprint package being used is consistent between builds and thiseas update
command when calculating the runtime version.How
In test bare app in expo/expo repo with all the modules installed locally (checked out to expo/expo#27119), run
neas update -p ios
and ensure the fingerprint matches.Test Plan
Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction.