Why your paywall fails App Review
The reviewer taps buy, nothing happens, you get rejected. Almost always one of these.
If you charge, App Review will try to buy it. When the paywall gets an app bounced, it’s usually one of three things — none of them obvious.
You didn’t attach the subscription to the version
This is the big one (Guideline 2.1). Creating the subscription in App Store Connect isn’t enough — you have to attach it to the specific app version and submit them together. If you don’t, the reviewer’s purchase can’t connect, and “it works on my phone” won’t save you. Your first subscription in particular must go up with the build.
You left a bypass flag on
While building, most people add a “force premium” switch to test locked features without paying. Ship with it on and one of two things happens: the reviewer never sees a paywall (so why is there a subscription?), or the whole app is quietly free. Turn it off before you archive — and confirm it’s off in the actual build you upload, not just in your head.
An empty offering (if you use RevenueCat)
A brand-new product shows “Could not check” until it propagates and your first version is submitted — that part’s normal. But if your offering is genuinely empty, the paywall loads nothing, the reviewer can’t buy, and you’re rejected. Confirm the products actually appear.
One more, and it isn’t a bug: give the reviewer a note on how to reach the paywall. If scoring is behind the wall, tell them “tap New Shoot → Start trial.” Don’t make them hunt for it.
The full playbook — every screen, in order — is in the guides.
Rather not wrestle with this yourself?
We handle the App Store Connect and Google Play submission for you — the listing, the errors, the resubmits — and get your app into review. See App Submission →