merge origin/main (cross-store text checker); macOS platform pitfall renumbered to 79

This commit is contained in:
CRTkafa 2026-10-20 03:06:16 +07:00
commit 9db7180eb9
35 changed files with 618 additions and 60 deletions

View file

@ -55,7 +55,7 @@ in-app purchases). Resubmit that same submission; never create a second one next
3. `storebound apple resubmit --build <n>` (dry run without `--yes`): the plan table shows the build to attach, the
submission reused, every item in it already or added, which REJECTED items are marked resolved, and the submit.
An app with a macOS (tvOS, visionOS) version too: it picks the platform whose version was rejected, and asks for
`--platform ios|macos|...` when both were (pitfall 77).
`--platform ios|macos|...` when both were (pitfall 79).
4. The owner's yes, then `storebound apple resubmit --build <n> --yes`: build n is attached by its number, missing
items go in, the REJECTED version item is marked resolved (`PATCH reviewSubmissionItems/{id}` `resolved: true`),
then it submits. Apple answers every submit with "Version is not ready to be submitted yet" (and the console's
@ -89,6 +89,11 @@ Plain, polite, specific; one guideline per paragraph; no blame, no threats, no "
- **2.3 Accurate metadata**: screenshots must show the real app (for a game: real gameplay); no prices, no "free"
claims for paid items, no other platforms' UI; keywords without competitor names; age rating answers that match
the content.
- **2.3.10 Accurate Metadata (other platforms)**: "Android", "Google Play", "Google Play Games" or another store in
any App Store text, often a What's New copied from notes shared with Play (store-pitfalls 77). Fix: remove the
lines (tag shared notes `[play]` / `[apple]`, `storebound whats-new apply`), `storebound check` must show no
`other platform` blocker, push with `apple listing --version x.y.z`, reply "removed the references to other
platforms" and resubmit. Play's mirror case is the Metadata policy (iOS, App Store, Game Center in Play text).
- **2.3.1 Hidden or undocumented features** (Play: Deceptive behavior): remote config, feature flags or a remote
paywall the review notes did not mention (`storebound scan` rule `remote-features`, store-pitfalls 74). Fix: say in
the notes which SDK changes what remotely; a business-model change needs a new review and a description update.