gplay validate

gplay validate

Canonical Google Play release-readiness report.

gplay validate --package <name> [flags]

Validate release readiness for Google Play.

This is the canonical pre-release verification command. It combines:

• local artifact checks
• local metadata and screenshot checks
• release notes validation
• remote Play track and listing state
• manual follow-up items for Console-only checks

Legacy local-only validators remain available as subcommands: gplay validate bundle gplay validate listing gplay validate screenshots gplay validate submission

Flag	Description	Default
--apk	Path to .apk file to validate	``
--bundle	Path to .aab bundle file to validate	``
--dir	Metadata directory to validate (legacy combined layout)	``
--listings-dir	Directory containing listing metadata	``
--output	Output format: json (default), table, markdown	json
--package	Package name (applicationId)	``
--pretty	Pretty-print JSON output	false
--release-notes	Release notes input: plain text, JSON array, or @file	``
--screenshots-dir	Directory containing screenshots grouped by locale/device type	``
--strict	Treat warnings as failures	false
--track	Target track to validate	production

gplay validate bundle

Validate an app bundle before upload.

gplay validate bundle --file <path>

Validate an Android App Bundle (.aab) file.

Checks:

• File exists and is readable
• File has .aab extension
• File is a valid ZIP archive
• Contains required bundle components

Flag	Description	Default
--file	Path to .aab bundle file	``
--output	Output format: json (default), table, markdown	json
--pretty	Pretty-print JSON output	false

gplay validate listing

Validate store listing metadata.

gplay validate listing --dir <path> [--locale <lang>]

Validate store listing metadata files.

Checks:

• Title length (max 30 characters)
• Short description length (max 80 characters)
• Full description length (max 4000 characters)
• Required fields present
• Valid UTF-8 encoding

Flag	Description	Default
--dir	Directory containing listing metadata	./metadata
--format	Metadata format: fastlane (default), json	fastlane
--locale	Specific locale to validate (optional)	``
--output	Output format: json (default), table, markdown	json
--pretty	Pretty-print JSON output	false

gplay validate screenshots

Validate screenshot images.

gplay validate screenshots --dir <path> [--locale <lang>]

Validate screenshot images for store listings.

Checks:

• Minimum 2 screenshots required per device type
• Maximum 8 screenshots per device type
• Valid image formats (PNG, JPEG)
• File is readable

Flag	Description	Default
--dir	Directory containing screenshots	./metadata
--locale	Specific locale to validate (optional)	``
--output	Output format: json (default), table, markdown	json
--pretty	Pretty-print JSON output	false

gplay validate submission

Compatibility alias for the canonical readiness command.

gplay validate submission --package <name> [--dir <path>] [--output json|table]

Run the canonical Google Play release-readiness report using the legacy validate submission entry point.

This command remains for compatibility, but new docs and workflows should use: gplay validate –package <name> [flags]

Flag	Description	Default
--dir	Directory containing listing metadata	./metadata
--format	Metadata format: fastlane (default), json	fastlane
--output	Output format: json (default), table, markdown	json
--package	Application package name	``
--pretty	Pretty-print JSON output	false
--release-notes	Release notes input: plain text, JSON array, or @file	``
--strict	Treat warnings as failures	false
--track	Target track to validate	production