proguard

Work with ProGuard/R8 mapping files

Commands

sentry proguard upload <path...>

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)

sentry proguard uuid <path>

Compute the UUID for a ProGuard mapping file

Arguments:

Argument	Description
<path>	Path to the ProGuard mapping file

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

Examples

Upload

# Upload a ProGuard/R8 mapping file (org/project auto-detected)
sentry proguard upload ./app/build/outputs/mapping/release/mapping.txt

# Upload multiple mapping files
sentry proguard upload mapping-app.txt mapping-lib.txt

# Upload with a specific UUID (overrides the computed UUID)
sentry proguard upload --uuid abcdef01-2345-6789-abcd-ef0123456789 mapping.txt

# Validate without uploading
sentry proguard upload --no-upload mapping.txt

UUID

# 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

Important Notes

• 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.
• Upload uses the Sentry chunk-upload protocol (DIF). Each mapping is bundled as proguard/<uuid>.txt.