Commands
proguard
Work with ProGuard/R8 mapping files
Commands
Section titled “Commands”sentry proguard upload <path...>
Section titled “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>
Section titled “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
Section titled “Examples”# Compute the UUID for a ProGuard/R8 mapping filesentry proguard uuid ./app/build/outputs/mapping/release/mapping.txt
# Output as JSON (includes the file path)sentry proguard uuid mapping.txt --jsonImportant Notes
Section titled “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 uuidcommand byte-for-byte.