Make the Debug UUID a deterministic value based on the proguard mapping file. #750
Conversation
This file contains 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
…e assertions that are irrelevant if UUID genrations is deterministic
…file as input for creating the UUID
romtsn
approved these changes
Aug 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📜 Description
Make sure that the debug UUID computation is deterministic and not cache based on the value of the proguard mapping file.
💡 Motivation and Context
multiple builds from the same commit with a shared build cache can cause mapping files to be overwritten when they are uploaded to Sentry.
💚 How did you test it?
New unit test cases were added
📝 Checklist
🔮 Next steps