Command Reference

GPC follows a consistent <domain> <action> [options] pattern for every command.

Common Workflows

Most users start with these:

# Full picture — releases, vitals, and reviews in one command
gpc status

# End-to-end: validate, upload, release
gpc publish app.aab --track beta --notes "Bug fixes"

# Upload to a specific track
gpc releases upload app.aab --track internal

# Promote between tracks
gpc releases promote --from beta --to production --rollout 10

# Analyze bundle size
gpc bundle analyze app.aab --threshold 150

All Commands

Core Workflow

Command	Description
status	Releases + vitals + reviews in one unified snapshot
publish	End-to-end validate, upload, and release
validate	Pre-submission checks
releases	Upload, promote, rollout, release notes, diff
tracks	Track configuration and management
listings	Store listings, metadata, images

Monitoring

Command	Description
reviews	User reviews and ratings
vitals	Crash rates, ANR, startup, rendering, battery, memory

Monetization

Command	Description
subscriptions	Subscriptions, base plans, offers
one-time-products	One-time products and offers (alias: otp)
purchase-options	Purchase option management for one-time products
iap	In-app products (legacy API)
purchases	Purchase verification, acknowledgment, refunds
pricing	Regional price conversion

Reporting & Team

Command	Description
reports	Financial and stats report downloads
testers	Tester management by track
users	Developer account users and permissions

Distribution

Command	Description
bundle	Local AAB/APK size analysis and comparison
internal-sharing	Review-free QA distribution
generated-apks	Device-specific APK downloads
device-tiers	Device capability targeting

Compliance & Recovery

Command	Description
data-safety	Data safety declarations
recovery	App recovery actions
external-transactions	External transactions (alternative billing)

System

Command	Description
auth	Authentication and profiles
apps	App info and configuration
config	CLI configuration
plugins	Plugin management
migrate	Migrate from Fastlane to GPC
doctor / docs / completion	Diagnostics, documentation, shell completions
install-skills	Install AI agent skills for GPC workflows

Global Flags

Every command accepts these flags:

Flag	Short	Type	Default	Description
--output	-o	string	auto	Output format: table, json, yaml, markdown
--quiet	-q	boolean	false	Suppress non-essential output
--verbose	-v	boolean	false	Enable debug logging
--profile	-p	string		Use a named auth profile
--app	-a	string		App package name (overrides config)
--no-color		boolean	false	Disable colored output
--no-interactive		boolean	false	Disable interactive prompts
--dry-run		boolean	false	Preview changes without executing
--limit		number		Max results per page
--next-page		string		Pagination token for next page
--retry-log		string		Log retry attempts to file (JSONL)
--config		string		Path to config file
--notify		string		Send webhook on completion (slack, discord, custom)
--sort		string		Sort results by field (prefix with - for descending)
--version	-V	boolean		Show version
--help	-h	boolean		Show help

Output Behavior

GPC auto-detects the output environment:

Context	Default Format	Reason
TTY (interactive terminal)	table	Human-readable formatted output
Non-TTY (pipe, redirect)	json	Machine-parseable for scripting
CI environment (CI=true)	json	Deterministic for automation

The --output flag overrides auto-detection in all cases.

Output Formats

table

gpc apps info com.example.app

Package Name   com.example.app
Title          My App
Default Lang   en-US

json

gpc apps info com.example.app --output json

{
  "success": true,
  "data": {
    "packageName": "com.example.app",
    "title": "My App",
    "defaultLanguage": "en-US"
  },
  "metadata": {
    "command": "apps info",
    "timestamp": "2026-03-09T12:00:00Z",
    "duration_ms": 342
  }
}

yaml

gpc apps info com.example.app --output yaml

success: true
data:
  packageName: com.example.app
  title: My App
  defaultLanguage: en-US
metadata:
  command: apps info
  timestamp: "2026-03-09T12:00:00Z"
  duration_ms: 342

markdown

gpc releases status --output markdown >> "$GITHUB_STEP_SUMMARY"

Produces a Markdown table suitable for GitHub Actions step summaries.

Error Output

All errors follow a consistent JSON structure:

{
  "success": false,
  "error": {
    "code": "AUTH_EXPIRED",
    "message": "Access token has expired",
    "suggestion": "Run 'gpc auth login' to re-authenticate"
  }
}

Exit Codes

Code	Meaning
0	Success
1	General error
2	Usage error (bad arguments)
3	Authentication error
4	API error (rate limit, permission denied)
5	Network error
6	Threshold breach (vitals CI alerting)
10	Plugin error

Environment Variables

Variable	Description	Default
GPC_SERVICE_ACCOUNT	Service account JSON string or file path
GPC_APP	Default package name
GPC_PROFILE	Auth profile name
GPC_OUTPUT	Default output format	auto
GPC_NO_COLOR	Disable color output
GPC_NO_INTERACTIVE	Disable prompts	Auto in CI
GPC_SKIP_KEYCHAIN	Skip OS keychain, use file storage
GPC_MAX_RETRIES	Max retry attempts on transient errors	3
GPC_TIMEOUT	Request timeout in milliseconds	30000
GPC_BASE_DELAY	Base retry delay in milliseconds	1000
GPC_MAX_DELAY	Max retry delay in milliseconds	60000
GPC_RATE_LIMIT	Requests per second	50
GPC_DEVELOPER_ID	Developer account ID (for user management)
GPC_CA_CERT	Custom CA certificate path
HTTPS_PROXY	HTTP proxy URL

Related

• Authentication Guide
• Configuration Guide
• CI/CD Integration
• Exit Codes Reference
• JSON Output Contract