gplay-submission-checks
Pre-submission validation for Google Play releases covering metadata, screenshots, bundle integrity, data safety, and policy compliance. Use when preparing a release to avoid rejections and catch issues before submitting.
tamtom · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add tamtom/gplay-cli-skills --skill gplay-submission-checksAbout this skill
name: gplay-submission-checks description: Pre-submission validation for Google Play releases covering metadata, screenshots, bundle integrity, data safety, and policy compliance. Use when preparing a release to avoid rejections and catch issues before submitting.
Google Play Submission Checks
Use this skill to validate everything before submitting a release to Google Play, reducing rejections and failed edits.
Preconditions
- Auth configured (
gplay auth loginorGPLAY_SERVICE_ACCOUNTenv var). - Package name known (
--packageorGPLAY_PACKAGE). - AAB/APK built and signed.
- Service account has at least "Release Manager" permission.
Prefer the First-Class Commands
The CLI has canonical, purpose-built commands. Reach for these before hand-scripting individual validators:
-
gplay validate --package <pkg>— the canonical release-readiness report. Combines local artifact/metadata/screenshot/release-note checks with remote track and listing state and Console-only follow-up items. Use--bundle,--listings-dir,--screenshots-dir,--track, and--strict(treat warnings as failures) to scope it.gplay validate \ --package com.example.app \ --bundle app-release.aab \ --track production \ --strict -
gplay preflight --file <app.aab>— offline AAB/APK compliance and hygiene. Fully decodesAndroidManifest.xml(binary AXML for APKs, aapt2 protobuf for App Bundles) and runs nine scanners:manifest,permissions,native_libs,metadata,secrets,billing,privacy,policy,size. No API calls and no credentials. Exit codes: 0 clean, 1 findings at/above--fail-on.gplay preflight --file app-release.aab --max-size 150M --fail-on warning # Validate the store listing in the same pass gplay preflight --file app-release.aab --listings-dir ./metadata --fail-on error # Narrow the gate gplay preflight --file app-release.aab --only manifest,permissions,native_libsSee the
gplay-preflightskill for what each scanner catches, how to read the findings, and CI gating patterns. -
gplay checks upload— Google Checks compliance analysis as a CI gate. Use--severity-threshold PRIORITYto fail the pipeline on high-priority failed checks before release.gplay checks upload \ --account "$CHECKS_ACCOUNT" \ --app "$CHECKS_APP" \ --binary app-release.aab \ --binary-type ANDROID_AAB \ --severity-threshold PRIORITY -
gplay publish track --strict— preflight + publish in one step. Builds the readiness report, stops on blocking issues (and warnings with--strict), then runs the release workflow only if preflight passes.gplay publish track \ --package com.example.app \ --track production \ --bundle app-release.aab \ --release-notes @release-notes.json \ --strict
The detailed per-artifact checks below remain useful for narrowing down a failure or for CI steps that gate on one concern at a time.
Pre-submission Checklist
1. Validate Bundle Integrity
gplay validate bundle --file app-release.aab
Checks:
- File exists and is readable
- File has
.aabextension - Valid ZIP archive structure
- Contains required bundle components (manifest, resources, dex)
If using APK instead:
gplay validate bundle --file app-release.apk
2. Validate Store Listing Metadata
gplay validate listing --dir ./metadata
Checks:
- Title: max 30 characters
- Short description: max 80 characters
- Full description: max 4000 characters
- Required fields present
- Valid UTF-8 encoding
Validate a specific locale:
gplay validate listing --dir ./metadata --locale en-US
For JSON format metadata:
gplay validate listing --dir ./metadata --format json
3. Validate Screenshots
gplay validate screenshots --dir ./metadata
Checks:
- Minimum 2 screenshots per device type
- Maximum 8 screenshots per device type
- Valid image formats (PNG, JPEG)
- Files are readable
Validate for a specific locale:
gplay validate screenshots --dir ./metadata --locale en-US
4. Verify Existing Listings on Play Store
Compare local metadata against what is live:
gplay sync diff-listings \
--package com.example.app \
--dir ./metadata
Check all configured locales:
EDIT_ID=$(gplay edits create --package com.example.app | jq -r '.id')
gplay listings list --package com.example.app --edit $EDIT_ID --output table
5. Data Safety Declaration
Ensure the data safety form is complete. Missing or inaccurate data safety declarations are a common rejection reason.
gplay data-safety update \
--package com.example.app \
--json @data-safety.json
6. Version Code Check
The version code must be strictly higher than all previous releases on every track. Check current track status:
gplay tracks list --package com.example.app --output table
Get details for a specific track:
EDIT_ID=$(gplay edits create --package com.example.app | jq -r '.id')
gplay tracks get --package com.example.app --edit $EDIT_ID --track production --output table
7. Deobfuscation / Mapping File
Upload ProGuard/R8 mapping files so crash reports in Play Console are readable.
This command is edit-scoped (needs --edit) and the version flag is
--apk-version, not --version-code:
EDIT_ID=$(gplay edits create --package com.example.app | jq -r '.id')
gplay deobfuscation upload \
--package com.example.app \
--edit $EDIT_ID \
--apk-version 42 \
--file mapping.txt
gplay edits commit --package com.example.app --edit $EDIT_ID
Without mapping files, crash stack traces in Android Vitals will be obfuscated and unusable.
8. Dry Run the Release
The safest pre-submission check. Performs the full release pipeline without committing:
gplay release \
--pa
Read the complete source ↗