Verify Play release config end-to-end: service-account credentials, PLAY_PACKAGE_NAME, and (if creds are present) that the package can be reached via the Android Publisher API. Run this first in any release session. No local toolchain check is needed — builds arrive pre-signed from EAS/Gradle.

Snapshot of every release track (internal, closed testing, open testing, production) and their current release: version codes, rollout status, staged-rollout percentage. Use this to answer 'where is the release right now?'

Upload a signed .aab (Android App Bundle) to Play — the bundle must already be built and signed (e.g. by eas build -p android). Returns the resulting versionCode; pass it to play_release_to_track to actually ship it to a track.

Assign an uploaded versionCode to a release track and publish it there. Targeting 'production' rolls the release out to all users (subject to Google's automated policy review) — this is the point of no return for a public release; confirm with the human first for production. Testing tracks (internal/alpha/beta, or a custom closed-testing track name) publish immediately with no review gate.

Update Play Store listing text for a locale: title, short description, full description. Note: only Play Console (web) can fill out the Data Safety form and content rating questionnaire — those have no public API.

Upload a store listing image: phone/tablet screenshots, the 512x512 hi-res icon, or the 1024x500 feature graphic. Unlike App Store Connect, Play's API supports uploading these directly — no Console click-through needed.

List recent user reviews with star ratings and text. No App Store Connect equivalent — Play exposes reviews directly via the API.

Post a public developer reply to a user review.