Fix Library
30 of 53 fiches — needs a new build.
1.2 Safety - User-Generated Content
1.6 Data Security
2.1 App Completeness
2.1 App Completeness App crashes on launch or during review Apple says your app crashed, froze, or bugged out when they launched or used it during review. 2.1 App Completeness In-app purchases not visible or not working during review The reviewer opens your paywall and sees no prices, an empty screen, a spinner, or a Continue button that does nothing — so they reject under 2.1. 2.1 App Completeness Rejected for an iPad bug even though your app is iPhone-only Apple rejected your app for a bug or broken layout on iPad, even though you built and tested it only for iPhone. 2.1 App Completeness Apple says your app looks unfinished, placeholder, or like a beta Apple flagged placeholder text, empty screens, 'coming soon' features, dead links, or wording that makes the app read as a beta or trial. 2.1 App Completeness Your paywall is empty because RevenueCat/StoreKit isn't configured in the build Your paywall renders no prices for the reviewer, and your logs show RevenueCat returning empty offerings — because the SDK key, bundle ID, or product sync is wrong in the build you actually shipped. 2.1 App Completeness Your subscription is stuck 'Waiting for Review' or won't attach to the build You go to submit and there's no way to attach your subscription to the version — the 'In-App Purchases and Subscriptions' section is missing, or the sub is stuck 'Waiting for Review' and you can't add it again with a new build.
2.3.1 Accurate Metadata
2.5.1 Software Requirements
2.5.4 Software Requirements
3.1.1 In-App Purchase
3.1.1 In-App Purchase External payment link or wrong monetization method (you must use In-App Purchase) Apple rejected you because your app sells digital content/features through a website, Stripe, or an external link instead of Apple's In-App Purchase. What you're allowed to do depends on which storefront you ship to — the US and the EU each have their own carve-out. 3.1.1 In-App Purchase In-app purchase products have not been submitted for review Your app got approved (or is stuck) but your in-app purchases sit in 'Waiting for Review' / 'Developer Action Needed' and never get reviewed, so the paywall is empty in production. 3.1.1 In-App Purchase Your app needs a way to restore previously purchased in-app products Apple rejected your app because it sells subscriptions or non-consumables but has no visible 'Restore Purchases' button — even though your app silently restores entitlements in the background, the reviewer couldn't find an explicit way to do it.
3.1.1 In-App Purchase (EU / Digital Markets Act)
3.1.2 Subscriptions
3.1.2 Subscriptions Terms of Use (EULA) and Privacy Policy links missing on the paywall Your app has an auto-renewable subscription and got rejected because the reviewer couldn't find a working Terms of Use (EULA) and/or Privacy Policy link on the subscription screen itself — even though those links exist in Settings or on your website. 3.1.2 Subscriptions Free-trial toggle paywall rejected (3.1.2) — the “RIP toggle” rejection wave Your paywall has a switch that turns a free trial on or off (default OFF, cheaper plan pre-selected), and App Review rejected it under 3.1.2 as confusing. This is the wave of rejections that started in mid-January 2026 against the popular 'trial toggle' design.
4.2 Minimum Functionality
4.2 Minimum Functionality Apple says your app is too simple (4.2 minimum functionality) Apple rejected your app for being too simple, too website-like, or not offering enough native value — even though it works. 4.2 Minimum Functionality Apple says your app is just a repackaged website (WebView / wrapper) Apple rejected your app as too close to a mobile website — a WebView wrapper or a repackaged web experience without enough native functionality.
4.8 Login Services
5.1.1 Data Collection and Storage
5.1.1 Data Collection and Storage Build rejected for a missing privacy manifest or an undeclared required-reason API After you upload a build, Apple emails you an ITMS-9105x notice — a required-reason API you use has no declared reason, or a third-party SDK you bundle has no privacy manifest or signature — and the build won't go through until you add one. 5.1.1 Data Collection and Storage Rejected because your camera / photos / location purpose string is too vague Apple rejected your app because a permission prompt's purpose string doesn't clearly explain why you need the data.
5.1.1(iv) Data Collection and Storage — Access
5.1.1(iv) Data Collection and Storage — Access Rejected 5.1.1: your ATT prompt appears after the user already declined your GDPR / AdMob consent form Your app shows both a consent form (AdMob UMP / GDPR / CMP) and the iOS App Tracking Transparency prompt, and Apple rejected the app for the order or the duplication of the two. 5.1.1(iv) Data Collection and Storage — Access Rejected 5.1.1(iv): your pre-permission screen has a 'Don't allow' button, an 'Allow' button, or opens Settings too early Apple rejected your app because the custom screen you show *before* the iOS permission dialog gives the user a way to decline, or its button is worded like a consent decision ('Allow', 'Accept', 'Enable', 'Grant') — or your app pushes the user to iOS Settings before they've actually denied anything.