apple resubmit after a rejection: iap-submit reuses the open review submission (UNRESOLVED_ISSUES gets only missing items and is resubmitted, a draft is reused, one waiting for or in review means nothing is sent), never a second draft; 409 ITEM_PART_OF_ANOTHER_SUBMISSION names the other submission instead of the list-lag message, a draft the run created is canceled and the named one used; submit retried with backoff and heartbeat while Apple says not ready yet; new apple resubmit --build <n> (build by number, plan table, --yes); apple status lists UNRESOLVED_ISSUES items and the resubmit command. Pitfall 30

skills/appstore-first-release/SKILL.md

@@ -90,6 +90,11 @@ answers the compliance facts no file proves, all in one batch at the start.
   and the version page has no "In-App Purchases and Subscriptions" section any more. If the version was already
   submitted without them: cancel the review submission (`storebound apple status --cancel-submission <id>`, the
   owner's yes), wait a minute, then `apple iap-submit --with-version` (pitfall 28).
+- Rejected (Invalid Binary, a crash, ...): the review submission stays open with UNRESOLVED_ISSUES and keeps the
+  version and its IAPs. Upload a fixed build, then `storebound apple resubmit --build <n>` (dry run with the plan
+  table), and after the owner's yes `--build <n> --yes`: it attaches build n, reuses that submission (no second
+  draft), adds only missing items and resubmits, retrying while Apple says "not ready to be submitted yet"
+  (pitfall 30, `review-rejections`). `apple iap-submit` reuses it the same way.
 - App Privacy (data types, purposes, linked, tracking) is UI-only and must be **published**, not just saved.
 - Export compliance unanswered = "Missing Compliance": `storebound apple encryption` (`export-compliance`).
 - ITMS-91053 / 91061 privacy manifest emails after upload: `privacy-manifest` skill.