App Store Connect In-App Purchase Setup: The Five Gates Before StoreKit Works
An in-app product can look finished in App Store Connect and still be invisible to your app. In practice, StoreKit only returns and sells a product when five separate conditions are satisfied: the account paperwork is complete, the bundle identifier is explicit, the product has reached the Ready to Submit state, a sandbox tester exists, and you are running on real hardware. Each condition fails quietly, so the fastest debugging method is to check them in order rather than guessing at code.
Gate 1: Account paperwork must be accepted first
Before any in-app purchase can be tested, the account holder has to accept the Paid Applications Agreement, supply tax details, and keep banking information current in App Store Connect. This is the most frequently missed step for developers new to in-app purchases, because nothing in the app reports it. The only symptom is that an SKProductsRequest comes back empty. If you are not authorized to edit agreements or financial details, you will need someone in your organization who is.
Gate 2: The bundle identifier must be explicit, not a wildcard
In-app purchases attach to one specific bundle identifier. A project still using a wildcard bundle ID can build and run, but it cannot test in-app purchases. Register the explicit identifier at developer.apple.com, then update the bundle identifier in the app's plist through Xcode so the two match.
A tempting alternative is to register two identifiers, for example a beta and a production version on the same device. That path requires duplicating every in-app purchase configuration, and the maintenance cost usually outweighs the benefit. A single identifier is the simpler default.
Gate 3: Products must reach Ready to Submit
Creating a product in App Store Connect is not the same as completing it. StoreKit will not return a product through SKProductsRequest until its status reads Ready to Submit. This is the second most common setup mistake: the product exists, but the setup stops halfway.
Three omissions typically hold a product back:
- No localization. At least one localization is required.
- No price. A price must be set.
- No screenshot. A placeholder image is acceptable while the purchase UI is still being built, but it must use proper iOS dimensions.
Use the product status as your checkpoint. If it does not say Ready to Submit, assume StoreKit will not see it.
Gate 4: A sandbox tester account is required
Sandbox is Apple's pre-release environment for testing purchases before they go live. Testing there requires a separate sandbox account, created in App Store Connect. Because you will likely create many of these over the life of an app, adopt a consistent naming and password pattern from the start so testers stay easy to identify and replace.
Gate 5: Purchases must run on a physical device
The simulator cannot complete an in-app purchase. It will often return real product data from an SKProductsRequest, which makes the limitation easy to misread as a code bug. The purchase attempt itself fails with a Cannot Connect to iTunes Store error. Move the test to a real device before investigating anything else.
Symptom-to-cause checklist
Use the observed behavior to choose which gate to inspect first.
Where each setting lives
The setup spans three surfaces, which is why steps get missed. The map below shows what belongs where.
Why the process feels harder than it is
None of the five gates is conceptually difficult. The friction comes from the layout: agreements and financial details live in one area of App Store Connect, identifiers in the developer portal, product state back in App Store Connect, and the bundle identifier again in Xcode. Because each surface reports failure differently, or not at all, developers end up treating a configuration problem as a StoreKit problem. Checking the gates in order removes most of that ambiguity.
| What you observe | Likely gate | What to check |
|---|---|---|
| SKProductsRequest returns an empty list | Gate 1 or Gate 3 | Paid Applications Agreement, tax and banking details accepted; product status is Ready to Submit |
| Product exists in App Store Connect but never appears in the app | Gate 2 or Gate 3 | Explicit bundle identifier registered and matched in Xcode; localization, price and screenshot present |
| Product data loads but the purchase fails with Cannot Connect to iTunes Store | Gate 5 | Running on a physical device rather than the simulator |
| Purchase flow cannot be started at all | Gate 4 | A sandbox tester account exists in App Store Connect |
The symptoms above reflect the configuration behavior described for App Store Connect and StoreKit at the time of the original guide. Apple's interfaces and requirements change; verify current behavior in Apple's documentation before relying on any single symptom.
| Surface | Setting | Requirement |
|---|---|---|
| App Store Connect | Paid Applications Agreement | Accepted before testing |
| App Store Connect | Tax information | Provided before testing |
| App Store Connect | Banking information | Updated before testing |
| developer.apple.com | Bundle ID | Explicit identifier registered, not a wildcard |
| Xcode | Bundle identifier in plist | Matches the registered identifier |
| App Store Connect | Product localization | At least one |
| App Store Connect | Product price | Set |
| App Store Connect | Product screenshot | Present, in proper iOS dimensions |
| App Store Connect | Product status | Ready to Submit |
| App Store Connect | Sandbox tester | Account created |
Field locations and labels in App Store Connect and Xcode are subject to change by Apple. Confirm the current location of each setting in Apple's own documentation.
Frequently asked questions
Why does SKProductsRequest return no products?
The two most common causes are incomplete account paperwork and products that have not reached Ready to Submit. Check that the Paid Applications Agreement is accepted with tax and banking details provided, then confirm each product has a localization, a price, a screenshot and the Ready to Submit status.
Can I test in-app purchases with a wildcard bundle ID?
No. In-app purchases are tied to a specific bundle identifier. Register an explicit identifier and update the bundle identifier in the app's plist through Xcode to match.
Why does the purchase fail in the simulator?
The simulator cannot complete in-app purchases. Product data may still load, but the purchase attempt fails with a Cannot Connect to iTunes Store error. Test on a physical device.
Do I need a real screenshot for an in-app product?
A screenshot is required for the product to reach Ready to Submit. A placeholder is acceptable while the purchase UI is still being built, but it must use proper iOS dimensions.