I previously responded to thread 840483, but Apple Support staff have not responded. I've also responded in App Review and created a support email, but the response times have been inadequate, and in the email thread it seems that the responding agent(s) did not read or understand the context of the issue, so I'll make this post in the hope that someone from Apple Support can assist.
Guideline 2.1(b) rejection, with no way to submit the in-app purchase and the version together.
I’m hitting the same deadlock described in thread link text, and I’ve added my case because it looks systemic, not a one-off setup error.
My situation
- New app, iOS 1.0. One non-consumable in-app purchase (Pro Unlock). All metadata, price, availability, and the App Review screenshot are complete, and its status is Ready for Review.
- Rejected first under 2.1 (information needed), then, after I resubmitted, under 2.1(b): the in-app purchase “has not been submitted for review.” Apple’s instruction was to submit the purchase and upload a new binary.
What I can’t do
- Adding the purchase for review creates a stand-alone Draft Submission that says: “Unable to Submit for Review. To submit your items for review, add an app version for the selected platform.” The version is never offered, and Submit stays disabled.
- The app version is held by the rejected submission, where the only option is Resubmit. That sends the version alone, which is what caused the rejection.
- The version page doesn’t show an “In-App Purchases and Subscriptions” section, so there’s nowhere to attach the purchase, contrary to what Apple’s help pages describe.
- I uploaded a new build, attached it to the version, deleted the stale draft, and tried every Add for Review path I could find. The result is the same.
Why this isn’t acceptable
App Review’s own message tells developers to do something that App Store Connect currently doesn’t allow. Everything Apple needs to see this is on Apple’s side: the account shows a configured purchase, a version in a rejected submission, and a draft that cannot be submitted. The state is visible without any information from me, yet the response so far is a rejection that repeats an instruction I can’t carry out. Each rejection costs developers days.
What I’m asking Apple to do
- Attach the in-app purchase to the existing submission for the version, or
- Release the version from the rejected submission, so a single new submission can contain both.
- Acknowledge whether this is a known App Store Connect issue, and when it will be fixed.
Other, older threads reporting similar issues and no posted solution include:
I’ve also contacted Developer Support and replied in the Resolution Center. Could an Apple staff member look at this thread and my submission (ID ef48c4f6-1ad2-46d8-bb95-46c20bffc82a)?
To anyone else with the same problem: please say so, and describe whether you found any workaround that didn’t require recreating your product IDs.