gplay releases mappings upload
Attach a ProGuard/R8 deobfuscation file (mapping.txt) to an already-published versionCode, after the fact, so Play vitals can symbolicate that version's obfuscated crash stacks.
Performs the full Edit lifecycle in one call: edits.insert → deobfuscationfiles.upload → edits.commit
To upload a mapping at the same time as the AAB (the common case), pass --mapping to gplay releases upload instead.
gplay releases mappings upload <mapping.txt> [flags]| Flag | Description |
|---|---|
--dry-run | validate inputs without any HTTP call |
--keep-edit-on-failure | skip the auto-discard cleanup on failure (debug) |
--output string | output format: table, json, or markdown (default: auto — table on TTY, json in pipes/CI) |
--package string | Android package name (overrides .gplay/config.json pin) |
--type string | deobfuscation file type: proguard or nativeCode (default "proguard") |
--version-code int | APK versionCode the mapping belongs to (required) |
Global flags
Section titled “Global flags”| Flag | Description |
|---|---|
--account string | name of a stored Account to use (overrides env and active Account) |
--retry int | retry transient failures (transport errors, 5xx, 429) up to N times with exponential backoff (default: 0, no retry) |
--service-account string | path to a service-account JSON, or inline JSON content (overrides --account, env, and active Account) |
--timeout duration | per-request API timeout, e.g. 30s or 2m (default: 60s for control-plane calls, none for uploads) |
-v, --verbose | log flow steps to stderr (info level) |