Rejection guides / Guideline 2.1(b): In-app purchases not found or not working
Guideline 2.1(b): in-app purchases the reviewer couldn't find or use
The reviewer tried to find or buy one of your in-app purchases and couldn't. Most of the time the problem is in App Store Connect setup, not in your code.
"If you offer in-app purchases in your app, make sure they are complete, up-to-date, visible to the reviewer and functional. If any configured in-app purchase items cannot be found or reviewed in your app, explain the reason in your review notes."App Review Guideline 2.1(b), Apple
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
What usually goes wrong
- The in-app purchase or subscription wasn't attached to the app version. An app's first in-app purchase has to be submitted together with a new app version.
- The product is missing metadata, such as a display name, description, price or the review screenshot, so it isn't ready for review.
- The Paid Applications agreement isn't active in App Store Connect, so products don't load in the review environment.
- The app asks the store for product IDs that don't match the ones in App Store Connect, so the paywall shows nothing or an error.
- The purchase screen is hard to reach, for example only after onboarding steps the reviewer skipped, or only for some regions.
- The app shows an empty state or a spinner when products fail to load, so the reviewer sees no way to buy.
How to fix it
- In App Store Connect, open each in-app purchase and subscription and make sure it's complete and selected on the app version you submit.
- Check Agreements, Tax and Banking and confirm the Paid Applications agreement is active.
- Test purchases with a sandbox account on a real device, from a fresh install, using the exact product IDs in your code.
- Show a clear message and a retry option if products fail to load, instead of an empty paywall.
- In App Review notes, say exactly where each purchase is, for example "Profile > Upgrade", and explain any product that isn't visible yet and why.
Common questions
- Do I need to submit a new build to fix 2.1(b)?
- Not always. If the problem was product setup or the agreement in App Store Connect, fixing that and replying may be enough. If the app's code loads the wrong product IDs or hides the paywall, you need a new build.
- What if some products aren't meant to be visible yet?
- Apple's guideline asks you to explain the reason in your review notes. Say which products they are and when they appear.
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
Related guides
- Guideline 3.1.1: In-App Purchase required
- Guideline 2.1: App Completeness (crashes, bugs, placeholders)
- Guideline 2.1: Information Needed
Apple decides every review. These guides explain what the guidelines say and what usually helps. They can't promise an approval.
Sources: App Review Guidelines (Apple)