feat(expo): Automatically detect Release name and version for Expo Web #4967
Conversation
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
10 tasks
antonis
approved these changes
Jul 3, 2025
There was a problem hiding this comment.
LGTM!
Tested both with a release and debug builds and worked as expected.
Awesome work @krystofwoldrich 🏅
Thank you the time to give feedback and contribute with this PR 🙇
antonis
reviewed
Jul 3, 2025
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.
📢 Type of change
📜 Description
This PR is an alternative to #4910 implementing automatic detection of the application name and version to form a Sentry Release for Expo Web.
The automatic release enabled the Expo Web to get automatic Session and Replays, without warnings and errors about missing release.
This PR uses the Expo Config retrieval from the previous PR, https://github.com/getsentry/sentry-react-native/pull/4910/files#diff-046edcb66effc01d1cb5c9b13fda59fe16c771580a217bc3f972f2f8ce576a03R38.
But implements a different way to inject the release into the JS bundle. It creates a new Virtual JS Module which adds the release value to the global vars.
This module is only added for web bundles, both dev and release.
💡 Motivation and Context
💚 How did you test it?
unit tests + sample app
📝 Checklist
sendDefaultPIIis enabled