CRT/storebound
1
0
Fork 0
Code Issues Pull requests Releases 1 Packages 1 Activity Actions

apple iap-submit: DEVELOPER_REJECTED IAP / subscription / group versions (left by a canceled submission) are submitted as they are, plan says 'add (developer rejected, re-submitted as is)', --new-version only for APPROVED / REJECTED, empty draft reused; fake ASC models cancel and re-add. play build / check: warn before Gradle when defaultConfig does not read -PversionCode / -PversionName, with the exact Groovy / Kotlin line (built with AGP 8.13); android.injected.version.code does not override bundleRelease; post-build versionCode mismatch is a hard stop. play-production-release plan: 'Do you want to restart your review?' dialog, Restart review is never-press. Pitfalls 31-33

Browse source
This commit is contained in:
CRTkafa 2026-10-12 11:32:05 +08:00
parent 41d2ffcc24
commit 0b1451800c
18 changed files with 399 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

3
skills/play-first-release/SKILL.md
View file

@ -91,6 +91,9 @@ products) and answers the compliance facts no file proves, all in one batch at t
deobfuscation file is only a warning) > Save.
c) Publishing overview > "Submit N changes for review" > dialog "Send N changes for review?" > **Send changes for
review**: the owner's final button, and it needs a real click (a JS `.click()` did nothing on it).
While a review is already running, "Submit N changes for review" opens **"Do you want to restart your
review?"** with **Restart review** instead: that restarts the running review with the new changes. It is the
owner's button too (never the agent's); Cancel leaves the running review alone.
Managed publishing is off by default: the app goes live automatically once Google approves it. If the owner wants
to pick the moment, they turn on Publishing overview > Managed publishing first; record it in
`play.managedPublishing` (`play release` and the plan warn while it is off).