gplay vitals
gplay vitals
Section titled “gplay vitals”App vitals: crashes, performance, and error reports.
gplay vitals <subcommand> [flags]gplay vitals crashes
Section titled “gplay vitals crashes”Query crash and ANR metrics.
gplay vitals crashes <subcommand> [flags]gplay vitals crashes query
Section titled “gplay vitals crashes query”Query crash or ANR rate metrics.
gplay vitals crashes query --package <pkg> [--from <date>] [--to <date>] [--dimension <dim>] [--type crash|anr]Query crash or ANR rate metrics from the Play Developer Reporting API.
Use –type to select between crash rate and ANR rate metrics. Use –dimension to group results by versionCode, deviceModel, etc. Date range can be specified with –from and –to in ISO 8601 format.
Note: This command uses the Play Developer Reporting API, which is separate from the Android Publisher API used by other commands.
| Flag | Description | Default |
|---|---|---|
--dimension |
Dimension to group by (versionCode, deviceModel, etc.) | `` |
--from |
Start date (ISO 8601, e.g. 2025-01-01) | `` |
--output |
Output format: json (default), table, markdown | json |
--package |
Package name (applicationId) | `` |
--paginate |
Fetch all pages | false |
--pretty |
Pretty-print JSON output | false |
--to |
End date (ISO 8601, e.g. 2025-01-31) | `` |
--type |
Metric type: crash (default) or anr | crash |
gplay vitals crashes anomalies
Section titled “gplay vitals crashes anomalies”List detected anomalies for crash, ANR, errors, and performance metrics.
gplay vitals crashes anomalies --package <pkg> [flags]List detected anomalies for vitals metrics.
Anomalies are automatically detected deviations in vitals metrics that may indicate a regression introduced by a new release.
Examples: gplay vitals crashes anomalies –package com.example.app gplay vitals crashes anomalies –package com.example.app –type anr gplay vitals crashes anomalies –package com.example.app –from 2026-03-01 –to 2026-03-31
Note: This command uses the Play Developer Reporting API, which is separate from the Android Publisher API used by other commands.
| Flag | Description | Default |
|---|---|---|
--from |
Start date (YYYY-MM-DD); defaults to 7d ago | `` |
--limit |
Maximum anomalies to return (1-1000) | 50 |
--output |
Output format: json (default), table, markdown | json |
--package |
Package name (applicationId) | `` |
--pretty |
Pretty-print JSON output | false |
--to |
End date (YYYY-MM-DD); defaults to today | `` |
--type |
Metric set: crash, anr, errors, performance, all | all |
gplay vitals performance
Section titled “gplay vitals performance”App startup, rendering, and battery performance metrics.
gplay vitals performance <subcommand> [flags]gplay vitals performance startup
Section titled “gplay vitals performance startup”Get app startup time metrics.
gplay vitals performance startup --package <name> [flags]Get app startup time metrics.
Returns cold, warm, and hot start duration percentiles for the specified package and date range. Use –dimension to break down results by API level, device model, or country.
| Flag | Description | Default |
|---|---|---|
--dimension |
Breakdown dimension (e.g. apiLevel, deviceModel, country) | `` |
--from |
Start date (YYYY-MM-DD) | `` |
--output |
Output format: json (default), table, markdown | json |
--package |
Package name (applicationId) | `` |
--paginate |
Fetch all pages | false |
--pretty |
Pretty-print JSON output | false |
--to |
End date (YYYY-MM-DD) | `` |
gplay vitals performance rendering
Section titled “gplay vitals performance rendering”Get slow rendering metrics.
gplay vitals performance rendering --package <name> [flags]Get slow rendering metrics.
Returns the percentage of frames that exceeded the 16ms and 700ms render time thresholds. Use –dimension to break down results by API level, device model, or country.
| Flag | Description | Default |
|---|---|---|
--dimension |
Breakdown dimension (e.g. apiLevel, deviceModel, country) | `` |
--from |
Start date (YYYY-MM-DD) | `` |
--output |
Output format: json (default), table, markdown | json |
--package |
Package name (applicationId) | `` |
--paginate |
Fetch all pages | false |
--pretty |
Pretty-print JSON output | false |
--to |
End date (YYYY-MM-DD) | `` |
gplay vitals performance battery
Section titled “gplay vitals performance battery”Get battery usage metrics.
gplay vitals performance battery --package <name> [flags]Get battery usage metrics.
Returns excessive wakeup or partial wake lock metrics. Use –type to select between “wakeup” (excessive wake-ups) and “wakelock” (stuck partial wake locks). Use –dimension to break down results by API level, device model, or country.
| Flag | Description | Default |
|---|---|---|
--dimension |
Breakdown dimension (e.g. apiLevel, deviceModel, country) | `` |
--from |
Start date (YYYY-MM-DD) | `` |
--output |
Output format: json (default), table, markdown | json |
--package |
Package name (applicationId) | `` |
--paginate |
Fetch all pages | false |
--pretty |
Pretty-print JSON output | false |
--to |
End date (YYYY-MM-DD) | `` |
--type |
Battery metric type: wakeup or wakelock | `` |
gplay vitals errors
Section titled “gplay vitals errors”Search error issues and reports.
gplay vitals errors <subcommand> [flags]Search grouped error issues and individual error reports.
Uses the Google Play Developer Reporting API to retrieve crash, ANR, and non-fatal error data for your application.
gplay vitals errors issues
Section titled “gplay vitals errors issues”Search grouped error issues.
gplay vitals errors issues --package <name> [flags]Search all error issues in which reports have been grouped.
Supported –filter fields: apiLevel, versionCode, deviceModel, deviceBrand, deviceType, errorIssueType (CRASH, ANR, NON_FATAL), appProcessState (FOREGROUND, BACKGROUND), isUserPerceived
Supported –order-by fields: errorReportCount desc, errorReportCount asc, distinctUsers desc, distinctUsers asc
Examples: gplay vitals errors issues –package com.example.app gplay vitals errors issues –package com.example.app –filter “errorIssueType = CRASH” gplay vitals errors issues –package com.example.app –order-by “errorReportCount desc” –page-size 10
| Flag | Description | Default |
|---|---|---|
--filter |
AIP-160 filter expression (e.g. ‘errorIssueType = CRASH’) | `` |
--order-by |
Order results (e.g. ‘errorReportCount desc’) | `` |
--output |
Output format: json (default), table, markdown | json |
--package |
Package name (applicationId) | `` |
--page-size |
Max results per page (1-1000) | 50 |
--paginate |
Fetch all pages | false |
--pretty |
Pretty-print JSON output | false |
gplay vitals errors reports
Section titled “gplay vitals errors reports”Search individual error reports.
gplay vitals errors reports --package <name> [flags]Search all error reports received for an app.
Returns individual error reports with stack traces and device info.
Supported –filter fields: apiLevel, versionCode, deviceModel, deviceBrand, deviceType, errorIssueType (CRASH, ANR, NON_FATAL), errorIssueId, errorReportId, appProcessState (FOREGROUND, BACKGROUND), isUserPerceived
Examples: gplay vitals errors reports –package com.example.app gplay vitals errors reports –package com.example.app –filter “errorIssueType = CRASH” gplay vitals errors reports –package com.example.app –filter “errorIssueId = 12345” –page-size 10
| Flag | Description | Default |
|---|---|---|
--filter |
AIP-160 filter expression (e.g. ‘errorIssueType = CRASH’) | `` |
--output |
Output format: json (default), table, markdown | json |
--package |
Package name (applicationId) | `` |
--page-size |
Max results per page (1-100) | 50 |
--paginate |
Fetch all pages | false |
--pretty |
Pretty-print JSON output | false |