Apple App Store & Google Play Submission Checklist: Preventing Rejections

1. The #1 Launch Blocker: Missing In-App Account Deletion & Privacy Manifests

If your app lets users create an account, Apple strictly requires an in-app option to initiate permanent account deletion (Guideline 5.1.1(v)), alongside an accurate PrivacyInfo.xcprivacy manifest declaring Required Reason APIs (file timestamps, user defaults, system boot time). Missing either triggers immediate binary rejection.

• Place 'Delete Account' clearly inside Profile -> Settings with confirmation safeguards and server-side token revocation.
• Verify every third-party native SDK in your Podfile includes valid privacy manifest declarations.

2. Subscriptions, Digital Goods & Restore Purchases (Guideline 3.1.1)

Apps selling digital content, AI credits, or SaaS unlocks on iOS/Android must route digital unlocks through Apple StoreKit / Google Play Billing (typically orchestrated via RevenueCat) and display clear billing duration, price, Privacy Policy, and Terms of Use links directly on the paywall.

• Include a visible 'Restore Purchases' button on the paywall screen that works without forcing double charges.
• Provide active Sandbox / Reviewer test credentials with pre-populated sample data in App Store Connect Review Notes so reviewers never hit an empty screen.

3. Background Location, BLE & Camera Permission Justifications

Both Apple reviewers and Google Play policy bots reject vague permission prompts like 'App needs location'. Permission strings must state the exact user benefit—and Android 14+ requires explicit foreground service types paired with a video walkthrough if requesting background location.

{
  "ios": {
    "infoPlist": {
      "NSLocationWhenInUseUsageDescription": "Used to calculate live turn-by-turn pickup routes and display nearby stations on the map.",
      "NSBluetoothAlwaysUsageDescription": "Used to pair directly with your charging station hardware when offline in underground garages."
    }
  }
}