Rejected submission

Update Review cannot attach the missing IAP

A careful path for a rejected version whose update flow still does not show the intended IAP.

Updating the rejected submission does not visibly collect the IAP and app version together.

An item-level state is not evidence that the purchase and app version are together in the review submission. Treat the draft contents as a separate checkpoint.

Inspect the active draft and item eligibility before repeating the same resubmission.

  1. 1Confirm required IAP or subscription metadata and the review screenshot.
  2. 2Verify the intended app version and active draft submission.
  3. 3Check agreements, tax, and banking status independently.
  4. 4Verify product lookup in sandbox or StoreKit testing.
  5. 5Escalate an observed UI limitation instead of guessing that it is fixed.

If linkage cannot be verified, keep the reply conditional and request App Store Connect support.

Keep the reply conditional.

Never state that the IAP was attached, reviewed, or resolved until the matching App Store Connect evidence supports that statement.

RECHECK ON SUBMISSION DAY

Apple’s official IAP submission instructions

Read at Apple Developer ↗

STRUCTURED SELECTIONS ONLY

Turn these checks into a complete resubmission map.

No rejection text, app identifiers, URLs, credentials, or arbitrary notes.

Get the map · $19 ↗