Hi everyone,
I’m trying to submit my first release with In-App Purchases, but I can’t keep the IAP attached to the submission.
Status: Not published yet (first release) Version: 5.0.0 (multiple builds: (7), (8), etc.)
What happens
I upload a new build and select it for version 5.0.0.
I go to Add for Review and select my newly created IAP (auto-renewable subscriptions).
I submit the version.
When I re-open the submission details, the IAP section is empty (they no longer appear as “Included in this submission”).
The result is a double failure:
App rejection (Guideline 2.1 – “IAP not found in the submitted binary”).
Each IAP is also rejected for lack of a binary in its review context.
It looks like the IAP and the build keep getting detached from each other after I submit. Since this is my first version, I’ve tried changing builds and even editing version metadata, but it still feels like I’m just “editing the first version” rather than creating a fresh link between this binary and these IAP.
What I already tried
Creating the IAP and selecting them during Add for Review.
Ensuring the IAP have complete metadata/localizations and pricing.
Re-submitting using a new build number (5.0.0 (8), etc.).
Checking Monetization → In-App Purchases and Subscriptions; products exist, but after submit they stop appearing under the submission.
(When testing the opposite path) Removing IAP entirely for a non-IAP release — but Review still referenced IAP “linked” on their side.
Questions
What is the exact, canonical sequence to link a new build to newly created IAP so they remain listed under “Included in this submission” after I hit Submit?
For first-time IAP, do I need to press Submit for Review on each IAP product before selecting them in the app submission? Or is selecting them during Add for Review enough?
Which product statuses are required so that IAP do not drop off the submission? (Ready to Submit vs Waiting for Review, etc.)
Can changing the build (or editing version metadata) after attaching IAP cause them to be silently removed from the submission?
Since this app is not yet published, is it advisable to create a new app version (e.g., 5.0.1) to “reset” the linkage, or should a new build under 5.0.0 be sufficient?
Any guidance or a step-by-step checklist to keep IAP attached to the submission would be greatly appreciated. Thanks!
— Victor