play-developer-console

Play Developer Console

Use the local Bun TypeScript CLI at:

/Users/jyo/projects/tools/play-cli

The CLI is linked locally with Bun and exposes:

play --help

For Moshi Android, run commands from:

/Users/jyo/projects/ai/moshi/marketing

The Play assets live in:

play/
  .env
  metadata/
  images/
  release-notes/

Workflow

• Inspect play/CLAUDE.md and relevant local files before changing store assets.
• Run one Play edit-backed command at a time. Do not parallelize play metadata, play app-info, play images, play bundle, or play tracks commands.
• Validate local listing text before upload:

• Use read-only checks before and after changes:

Release Workflow

Use the built-in track commands for release operations. Do not write ad hoc scripts against src/api.ts for normal release tasks.

Attach or update a release already uploaded to Play:

Prepare a production draft with release notes:

If a draft app has stale releases that block validation, clear the track first, then create the intended release:

When no --notes flag is provided, play tracks release reads all files in play/release-notes/ as localized release notes. Use --no-notes only when intentionally omitting notes.

• For bugs or missing Play API behavior, patch /Users/jyo/projects/tools/play-cli, then run:

Retry from /Users/jyo/projects/ai/moshi/marketing after the fix.

Auth

Moshi uses keyless local auth via gcloud ADC and a quota project in play/.env. Do not create or require service account JSON keys unless the user explicitly asks.

Expected env keys: