Fix dex-derived BuildUUID for proguard uploads #92
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.
Goal
Attempt to automatically derive a buildUuid from the
classes.dex
files formapping.txt
files.Design
If the
buildUuid
for a proguard file is not specified as either an option, or in theAndroidManifest.xml
then the tool will attempt to locate the appropriateclassesN.dex
files for themapping.txt
file, and derive the BuildUUID from these.Added a new
--no-build-uuid
(which is mutually exclusive with--build-uuid
) to the various Android upload options. If this is specified thebuildUuid
is set to""
and no attempt is made to find or generate a BuildUUID.Testing
Manually tested