Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    App Store & Play Rejection Fixer

    1

    Paste an App Review or Google Play rejection; your agent quotes the exact rule, finds the cause in your Expo, React Native, Flutter or native code, fixes it and writes the reply.

    $24

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    App Store & Play Rejection Fixer

    App Store & Play Rejection Fixer

    Example session with this skill installed

    Apple rejected v2.4.0 of our Expo app (SDK 57, Supabase auth, Google Sign-In). Guideline 5.1.1(v) "The app supports account creation but does not include an option to initiate account deletion", Guideline 4.8 Login Services, and Guideline 2.1 "an error message was displayed when we tapped Continue with Google", Device type: iPad Air (5th generation), OS version: iPadOS 26.0. Fix it and write the reply.

    • Read your context and instructions
    • Compiled the app store

    Summary

    Three valid findings, so fix and reply, no appeal. The pre-submission scan also caught a vague photo-library purpose string the reviewer hadn't flagged yet.

    1. Parsed rejection

    Platform: apple
    Review device: iPad Air (5th generation), iPadOS 26.0
    
    5.1.1(v)  Account Sign-In and account deletion  [explicit: exact]
    4.8  Login Services  [explicit: exact]
    2.1(a)  App Completeness: crashes, bugs, placeholder content  [narrowed by message wording]
    

    Rule quoted from the catalog: "If your app supports account creation, you must also offer account deletion within the app."

    2. Pre-submission scan

    ERROR ACCOUNT-DELETION-MISSING [5.1.1(v)]
          Account creation detected (src/auth.ts) but no in-app account deletion path found.
    WARN  IOS-NO-SIWA [4.8]
          Third-party login (@react-native-google-signin/google-signin) without Sign in with Apple.
    WARN  IOS-PURPOSE-VAGUE [5.1.1(ii)]
          NSPhotoLibraryUsageDescription is a library default: "Allow $(PRODUCT_NAME) to access your photos".
    

    3. Fixes

    Server-side hard delete with the service role, never in the app:

    const { data: userData, error: userError } = await admin.auth.getUser(accessToken);
    if (userError || !userData.user) return { ok: false, error: "invalid session" };
    await admin.from("profiles").delete().eq("id", userData.user.id);
    const { error } = await admin.auth.admin.deleteUser(userData.user.id);
    
    {
      "expo": {
        "ios": { "usesAppleSignIn": true },
        "plugins": [
          ["expo-image-picker", { "photosPermission": "Acme uses your photo library so you can attach a receipt to an expense." }]
        ]
      }
    }
    

    Plus Sign in with Apple buttons next to Google, Apple token revocation on deletion, and the iPad Google error fixed and tested on the device named in the message.

    4. Reply for App Store Connect

    Hello App Review team,
    
    Thank you for the review of version 2.4.0. We addressed each issue in build 62:
    
    Guideline 5.1.1(v): Account deletion is now in Profile > Settings > Delete account. It deletes the account and its data after confirmation, warns subscribers that billing continues through Apple until they cancel, and revokes Sign in with Apple tokens.
    Guideline 4.8: Sign in with Apple is offered next to Google Sign-In on the sign-in and sign-up screens. It requests only name and email and supports Hide My Email.
    Guideline 2.1: The error on "Continue with Google" on iPad is fixed and tested on iPad Air (5th generation), iPadOS 26.0.
    
    The demo account in App Review Information is unchanged.
    

    Connects securely to your tools. The creator never sees your data.

    About this skill

    When an app is rejected, agents paraphrase guidelines from memory, fix the first issue and miss the other two, appeal things that need a code change, and write replies that argue instead of answering. This pack replaces the guessing with a verified catalog and two scripts.

    What's inside

    • Verbatim, sourced policy text. 36 Apple entries and 22 Google Play entries, each with the official text checked line by line against the source page, the URL, what reviewers actually check, the likely cause per stack, the fix and a reply template.
    • Real failure modes, verified from source. expo-media-library adds READ_MEDIA_IMAGES/VIDEO by default, which triggers Play's Photo and Video Permissions policy. Expo plugins write default purpose strings that fail 5.1.1(ii). expo-tracking-transparency adds AD_ID on Android. ATT prompts requested before the app is active never show, so reviewers cite 2.1. Supabase deleteUser(id, true) is a soft delete that does not satisfy either store. Flutter's discontinued wakelock plugin triggers ITMS-91061. Expo SDK 53 and React Native 0.80 target API 35 and are now refused by Play.
    • Decide before you code. A fix-vs-clarify-vs-appeal table, Apple's App Review Board and expedite rules, Bug Fix Submission offers, Play's one-appeal-per-enforcement rule.

    Scripts included

    • parse-rejection.mjs maps pasted text (guideline numbers, sub-clauses like 4.3(a), ITMS codes, Play policy names) to catalog entries and pulls out the review device and version codes.
    • presubmit-check.mjs scans a project for the top causes: no account deletion, Google login without Sign in with Apple, undeclared required reason APIs, SDKs without privacy manifests, default purpose strings, ATT never requested, targetSdk below 36, restricted permissions with the library that added them, placeholder text, missing privacy policy link, and Kids/Families issues.

    Skills

    store-rejection-fixer (entry), review-replies-appeals, ios-privacy-manifest-att, account-deletion-login, play-permissions-data-safety, review-access-metadata, presubmit-scan.

    Policy text as of Apple's June 8, 2026 guidelines and Google Play policy articles retrieved 2026-10-13.

    Does not support Amazon Appstore or Huawei AppGallery. Requires manual access to App Store Connect or Play Console. Metadata-only fixes must be applied in the store dashboard.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    expo
    Node.js
    install-expo-modules

    Permissions

    Terminal / Shell
    Read Files
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill automates the interpretation of App Store and Google Play rejection notices, maps them to specific code-level issues in your project, and provides the exact technical fixes or appeal text needed to get approved.

    The skill is fully compatible with major cross-platform frameworks like React Native, Flutter, and Expo, as well as native Swift, Kotlin, and Java projects.

    It quotes the current official text instead of paraphrasing from memory: 36 Apple and 22 Google Play entries copied from the source pages and checked line by line, plus a scanner that finds the technical causes reviewers cite, like missing privacy manifests or default permission strings.

    No, for security reasons, the skill identifies the necessary changes and generates the code or metadata updates for you to review and apply within your own development environment.

    Seven skills, the verified Apple and Google Play policy catalogs with reply templates, and two zero-dependency Node scripts: parse-rejection.mjs, which maps a pasted rejection to catalog entries, and presubmit-check.mjs, which scans a project for the most common rejection causes.

    Every catalog entry records the date its text was retrieved from Apple's App Review Guidelines or the Google Play Policy Center, so outdated rules are easy to spot. The pack is reviewed when Apple or Google publish guideline changes.

    New in Mobile Development