Skip to content
DocsGitHub

proguard

Work with ProGuard/R8 mapping files

Upload ProGuard/R8 mapping files to Sentry

Arguments:

Argument Description
<path...> Paths to ProGuard/R8 mapping files

Options:

Option Description
--uuid <uuid> Force a specific UUID instead of computing from file content (only valid with a single file)
--no-upload Compute and print UUIDs without uploading (dry-run)
--require-one Require at least one mapping file (error if none provided)

Examples:

Terminal window
# Upload a ProGuard/R8 mapping file
sentry proguard upload ./app/build/outputs/mapping/release/mapping.txt
# Upload multiple mapping files
sentry proguard upload mapping-release.txt mapping-debug.txt
# Validate without uploading
sentry proguard upload mapping.txt --no-upload
# Fail if no mapping files are found (useful in CI)
sentry proguard upload ./mapping/ --require-one
# Upload with an explicit UUID
sentry proguard upload mapping.txt --uuid 5db7294d-87fc-5726-a5c0-4a90679657a5

Compute the UUID for a ProGuard mapping file

Arguments:

Argument Description
<path> Path to the ProGuard mapping file

Examples:

Terminal window
# Compute the UUID for a ProGuard/R8 mapping file
sentry proguard uuid ./app/build/outputs/mapping/release/mapping.txt
# Output as JSON (includes the file path)
sentry proguard uuid mapping.txt --json

All commands support --json for machine-readable output and --fields to select specific JSON fields.

  • The UUID is deterministically derived from the mapping file contents — identical files always produce the same UUID. This is the same value Sentry uses to associate a mapping with obfuscated Android stack traces.
  • This matches the UUID computed by the legacy sentry-cli proguard uuid command byte-for-byte.