Keep older dev clients usable without Expo sharing#20
Merged
Conversation
patroza
force-pushed
the
fix/optional-expo-sharing
branch
from
July 25, 2026 06:03
e115818 to
b8ccd7a
Compare
patroza
added a commit
that referenced
this pull request
Jul 25, 2026
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
1 participant
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.
Summary
ExpoSharingas an optional native moduleRoot cause
Raw Metro development sessions do not enforce the EAS runtime fingerprint. An older iOS dev client can therefore load current JavaScript that imports the newer native
ExpoSharingmodule and crash before rendering.Verification
vp run --filter @t3tools/mobile typecheckgit diff --checkIntegrated device verification is unavailable on this Linux host: neither Xcode nor an Android emulator is installed. The reported iPhone is the affected physical device.