Fingerprint Update and Environmental Variable SE #20
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
thinkocapo
changed the title
ndmanvar
approved these changes
Jan 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Overview
Every new release we publish and run tests against will produce the same issues every time because they have the same fingerprints.
This PR introduces an update to the fingerprint using the release number(same technique as used in application-monitoring-javascript), so that when a new release is published, the fingerprint is unique to the release.
An SE tag can be set in .env so you can differentiate events from a React Native on your machine versus events from React Native in saucelabs.
Test - Fingerprint Update
Here's the issue Id (fingerprint) for the handled exception, before updating the fingerprinting algorithm.
WILL-REACT-NATIVE-6 issue link
Here's the issue Id (fingerprint) for the handled exception, after updating the fingerprinting algorithm to take the Release into consideration:
WILL-REACT-NATIVE-8 issue link
Lastly, this produced New Issues, which you can see in Release Health for the 2.0.7 release
Test - Environmental Variable SE
WILL-REACT-NATIVE-B
WILL-REACT-NATIVE-C
and you can see the difference here:
If you don't provide any .env file then the app still runs, and the SE variable will get ignored in source code.