Guideline 3.1.1 – Consumable IAPs rejected after binary approved; asked for “new binary” though 1.8 already submitted

Hi,

We received App Review feedback under Guideline 3.1.1 for our in-app purchases, and we’d appreciate guidance on the expected next step.

What we submitted;

  • We created and completed metadata for the new consumable IAPs (pricing, availability, review screenshots, localizations).
  • We uploaded and submitted app version 1.8 with a recent binary (build processed/VALID in App Store Connect).

We also submitted the consumable IAPs for review. Outcome:

  • App version 1.8 was approved (currently Pending Developer Release).

  • The consumable IAPs were returned with Developer Action Needed.

Our confusion

We already uploaded/submitted a new binary (1.8) for this release, and the consumable purchase flows are implemented in that binary (Store / offers). The app binary itself was approved, but the consumable IAPs were rejected with a request for another new binary.

For a first-time expansion from Non-Consumable-only to Consumables, is a separate / subsequent binary submission always required even if the approved version already contains the purchase UI?

After being stuck in review for 2 months, my IAPs were approved just 4 hours after I posted here

Guideline 3.1.1 – Consumable IAPs rejected after binary approved; asked for “new binary” though 1.8 already submitted
 
 
Q