[PB-6219]: use fingerprint policy for runtimeVersion to prevent update check failures#411
Closed
terrerox wants to merge 1 commit intorelease-v1.9.1from
Closed
[PB-6219]: use fingerprint policy for runtimeVersion to prevent update check failures#411terrerox wants to merge 1 commit intorelease-v1.9.1from
terrerox wants to merge 1 commit intorelease-v1.9.1from
Conversation
…k failures Users on older app binaries experienced checkForUpdateAsync rejections because runtimeVersion was tied to package.json version, causing mismatches when no OTA update existed for their runtime version
|
CandelR
reviewed
Apr 14, 2026
Contributor
CandelR
left a comment
CandelR
left a comment
There was a problem hiding this comment.
It is okay 🆗 . But need to create a branch with the number of release in order to merge all task to that branch. E.g: release-v1.9.1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Previously, runtimeVersion was set to the package.json version (e.g. "1.8.6"). This meant every version bump changed the runtimeVersion, causing users on older binaries to fail when calling checkForUpdateAsync — the Expo update server had no OTA update for their outdated runtimeVersion, rejecting the request with "Failed to check for update".
Switching to the fingerprint policy generates a hash based on native dependencies, so runtimeVersion only changes when native code changes — not on JS-only version bumps. This allows OTA updates to reach all compatible binaries regardless of package version.
Also added a logger.warn before the Sentry report for better diagnostics.
See: https://docs.expo.dev/eas-update/runtime-versions/#fingerprint-runtime-version-policy