Gpd Submission Health

GPD Submission Health

Iron Law

NEVER SUBMIT TO PRODUCTION WITHOUT COMPLETING ALL 5 PREFLIGHT CHECKS — A FAILED RELEASE BLOCKS ALL USERS ON THAT TRACK

Read reference/submission-preflight-checklist.md and complete every item before running any production release command.

Preconditions

• Auth configured and package name resolved.
• Build uploaded and available for the target track.
• Store listing metadata and assets updated.

Pre-submission Checklist

The full 5-step checklist with commands is in reference/submission-preflight-checklist.md.

Quick reference — all 5 steps must pass before releasing to production:

1. Validate edit — gpd publish edit validate must return no errors
2. Confirm release status — version code matches uploaded build
3. Verify store listing metadata — title, description, contact email present
4. Verify screenshots and assets — required device types uploaded per locale
5. Upload deobfuscation mapping — required if ProGuard/R8 is enabled

For full commands for each step: Read reference/submission-preflight-checklist.md

Submit to production

gpd publish release --package com.example.app --track production --status inProgress --version-code 123

Common submission issues

Release not in valid state

Check:

1. Version code uploaded and attached to the track.
2. Edit validation passes.
3. Required store listing fields present for all locales.

Missing screenshots or assets

gpd publish images list phoneScreenshots --package com.example.app --locale en-US
gpd publish images upload icon icon.png --package com.example.app --locale en-US

Policy declarations not complete

Some policy/compliance items must be completed in Play Console UI. Confirm in the console if CLI operations pass but submission is blocked.

Notes

• Use gpd publish edit validate before committing large changes.
• Use --dry-run where available before destructive actions.

Documentation Sources