gplay apps add
Register an Android package name (e.g. com.example.myapp) under
the active Account in gplay's local registry. By default apps add
validates access by opening and immediately discarding a Google Play
Edit on the package — a cheap probe that catches typos and missing
per-app permission grants at registration time rather than weeks later
in CI.
Pass --no-verify to skip the API round-trip (useful for offline or preparatory registration).
gplay apps add <package> [flags]| Flag | Description |
|---|---|
--no-verify | skip the edits.insert+delete access probe (record the package unconditionally) |
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) |