Store rejections
The rules that keep Fictura-powered apps out of rejection trouble — and what to check if a review comes back negative anyway.
The web-checkout rules that matter
- System browser, never a webview. Card entry for digital goods inside a webview your app controls is the one version of link-out Apple still rejects. The SDK enforces this — it hands the URL to the OS and your app loses control of the page. If a reviewer sees a payment sheet in-app, the build predates SDK 0.6.1.
- US-only by default — where Apple's external-purchase-link rules are clear. Widening the country list is a decision to make deliberately, not a default.
- Served paywall designs can't reach the open web. The webview only loads its own document — no navigation, no storage, no new windows — so a design can never turn into an unreviewed browsing surface.
If a rejection lands
Read the review state in the dashboard.
Dashboard → Products mirrors Apple's states — REJECTED and DEVELOPER_ACTION_NEEDED show exactly where Apple stopped. Product-level rejections (missing metadata, price/territory gaps) are fixable from the same page.
Don't wait for a re-review to change behavior.
Paywall copy, screens, targeting, and the web-checkout toggle are all server-side — you can comply now on every installed device, then resubmit the binary on your own schedule.
Roll back what you must.
Web checkout off returns everyone to the App Store sheet within one config refresh; a paywall can be swapped the same way. No emergency release.
The submission itself stays human
Fictura can create and price subscriptions through App Store Connect, but Apple requires a person to submit products for review with a binary. Budget for that click.