gplay vitals errors reports
Search individual error reports — the platform-produced stack traces — over a window.
gplay vitals errors reports --package com.example.app gplay vitals errors reports --filter "versionCode = 123" --since 7d --limit 10
NOTE: stack frames are obfuscated until you upload ProGuard/R8 mappings (gplay releases mappings upload — #250); until then frames are not symbolicated.
The full report text is in --output json; the table shows the first line. Read-only; --output json mirrors the API response verbatim.
gplay vitals errors reports [flags]| Flag | Description |
|---|---|
--filter string | AIP-160 filter, e.g. "versionCode = 123" |
--limit int | max reports to return (0 = all, no cap) |
--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) |
--since string | window length back from now, e.g. 28d or 24h (default "28d") |
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) |