Compare Android build artifacts

compare-buildsskillsetup L2★1

What it does

Compare two Android release artifacts for differences

Best for

Release validation workflows where you need to confirm that a new build only includes intended changes (size, permissions, ABI support) before distribution.

Inputs

· Two APK or AAB file paths

Outputs

· HTML comparison report
· File size and composition changes
· Package/version/SDK metadata diff
· Permissions, components, deep links
· Native library ABI changes
· Certificate fingerprint match status
· AAB module/delivery differences

Requires

· apkanalyzer (APK)
· bundletool (AAB)
· apksigner (signatures)
· android-artifact-comparator
· android-artifact-report-generator

Preconditions

· Both APK/AAB files exist and are valid
· apkanalyzer or bundletool available as applicable

Failure modes

· One or both artifacts missing or corrupted
· apkanalyzer/bundletool not in PATH or SDK locations
· Mixed APK+AAB input (only APK-to-APK or AAB-to-AAB supported)

Trust signals

· Explicit expected-vs-blocker-vs-unknown classification
· Multiple tool invocations documented
· Safety rules prevent artifact execution