doctor / docs / completion
Utility commands for environment verification, documentation access, and shell completions.
Commands
| Command | Description |
|---|---|
doctor | Verify setup and connectivity |
docs | Open documentation in browser |
completion bash | Generate bash completions |
completion zsh | Generate zsh completions |
completion fish | Generate fish completions |
gpc doctor
Run diagnostic checks to verify your GPC setup end-to-end.
Synopsis
gpc doctor [--json]Options
| Flag | Description |
|---|---|
--json | Output results as machine-readable JSON |
Checks performed
| Check | What it verifies |
|---|---|
node | Node.js ≥ 20 |
config | Config file loads without errors |
default-app | A default package name is configured |
package-name | Package name matches Android naming rules |
config-dir | Config directory is readable and writable |
cache-dir | Cache directory is readable and writable |
service-account-file | SA key file exists and is readable (if configured) |
service-account-permissions | SA key file is not group/world-readable (Unix) |
profile | GPC_PROFILE env var points to a known profile |
proxy | Proxy URL is valid (if HTTPS_PROXY etc. are set) |
ca-cert | CA cert file exists (if GPC_CA_CERT is set) |
dns | Both API endpoints resolve: androidpublisher.googleapis.com and playdeveloperreporting.googleapis.com |
auth | Credentials load and authenticate successfully |
api-connectivity | Access token can be obtained from Google |
Example
gpc doctorAll checks passing:
GPC Doctor
✓ Node.js 22.12.0
✓ Configuration loaded
✓ Default app: com.example.myapp
✓ Package name format OK: com.example.myapp
✓ Config directory: /Users/you/.config/gpc
✓ Cache directory: /Users/you/.cache/gpc
✓ Service account file: /path/to/key.json
✓ Service account file permissions OK (mode: 600)
✓ DNS: androidpublisher.googleapis.com
✓ DNS: playdeveloperreporting.googleapis.com
✓ Authenticated as play-api@my-project.iam.gserviceaccount.com
✓ API connectivity verified
✓ 12 passed ⚠ 0 warnings ✗ 0 failed
All checks passed!With failures:
GPC Doctor
✓ Node.js 22.12.0
✗ Configuration could not be loaded
Run gpc config init to create a config file, or check .gpcrc.json for syntax errors
✓ 1 passed ⚠ 0 warnings ✗ 1 failed
Some checks failed. Fix the issues above and run again.JSON output
gpc doctor --json{
"success": true,
"errors": 0,
"warnings": 0,
"checks": [
{ "name": "node", "status": "pass", "message": "Node.js 22.12.0" },
{ "name": "config", "status": "pass", "message": "Configuration loaded" }
]
}Exits 0 if all checks pass, 1 if any check fails.
gpc docs
Open the GPC documentation in your default browser.
Synopsis
gpc docsOptions
No command-specific options.
Example
gpc docsOpens https://github.com/yasserstudio/gpc#readme in the default browser. If the browser cannot be opened, prints the URL to stdout.
completion bash
Generate bash shell completions. Pipe the output to your bash completions directory or source it directly.
Synopsis
gpc completion bashOptions
No command-specific options.
Example
Add to your .bashrc:
eval "$(gpc completion bash)"Or save to completions directory:
gpc completion bash > /etc/bash_completion.d/gpcOr for user-local completions:
mkdir -p ~/.local/share/bash-completion/completions
gpc completion bash > ~/.local/share/bash-completion/completions/gpccompletion zsh
Generate zsh shell completions.
Synopsis
gpc completion zshOptions
No command-specific options.
Example
Add to your .zshrc:
eval "$(gpc completion zsh)"Or save to your fpath:
gpc completion zsh > "${fpath[1]}/_gpc"Or for Oh My Zsh users:
gpc completion zsh > ~/.oh-my-zsh/completions/_gpccompletion fish
Generate fish shell completions.
Synopsis
gpc completion fishOptions
No command-specific options.
Example
Save to fish completions directory:
gpc completion fish > ~/.config/fish/completions/gpc.fishOr load for the current session:
gpc completion fish | sourceRelated
- auth -- Fix authentication issues flagged by doctor
- config -- Fix configuration issues flagged by doctor
- Installation Guide -- Initial setup