能否先定义In App Purchase且提交App审核时不包含？相关技术咨询

Hey there, let's break down your questions about In-App Purchases (IAP) clearly:

First, In-App Purchase (IAP) is Apple's official system that lets developers sell digital content or services directly within an app. This covers one-time purchases (like premium features, digital books), consumables (such as in-game coins), and auto-renewable subscriptions (the type you're planning to add).

As for submitting an app without using IAP: Absolutely yes. You don’t have to integrate IAP into your app unless your business model requires selling digital content/services through the app. Apple only enforces IAP usage if you’re offering digital goods that need to be purchased within the app—if your app has no such content, you can submit it for review normally without touching IAP at all.

Short answer: No, you can't exclude already-defined IAPs from the app review process once they're linked to your app ID and set to "Ready to Submit". When you submit your main branch for review, any IAPs associated with your app that are in a submission-ready state will automatically be included in the review queue.

But don’t worry—here are a few solid workarounds to handle this scenario:

• Delay creating IAPs in App Store Connect: Wait until your IAP development branch is fully tested and merged into the main branch. Then create the auto-renewable subscription entries in App Store Connect, and submit the app + IAPs together for review. This is the most straightforward approach and avoids conflicts with your weekly main branch updates.
• Keep IAPs in a non-submittable state: If you need to create the IAPs early (for sandbox testing, for example), make sure to leave them in the "Prepare for Submission" state (don’t mark them as "Ready to Submit"). If you accidentally submitted them, you can withdraw the IAP review request. This way, when you submit your main app update, these IAPs won’t be pulled into the review process.
• Ensure no IAP references exist in the main branch: For your weekly main branch submissions, double-check that your app code doesn’t include any references to the unready IAPs—no subscription buttons, no calls to fetch the product IDs, no related UI elements. While Apple might not flag this if they can’t find any IAP-related functionality in the app, this is riskier than the first two options, so use it only if the other solutions aren’t feasible.

内容的提问来源于stack exchange，提问作者talsharonts