Free, no sign upRuns in your browserNothing is uploaded
Store
App Store and Google Play rejection decoder
Rejection emails are written in policy language. This free rejection decoder turns guideline numbers like 4.2 Minimum Functionality or 5.1.1 Data Collection into plain English, with what it means, why it happens and how to fix it.
The rejections we see most
4.2: the app is too much like a website. Common for wrappers and web-only AI builder output.
2.1: crashes, broken links or no working demo account.
5.1.1: privacy policy, permissions and account deletion.
4.2.6: apps created from a template or app generation service that were not submitted by the content owner.
The decoder is a guide, not legal advice. Reviewers apply the rules themselves, and the wording of the guidelines changes, so always read your rejection message and the current guidelines too.
Frequently asked questions
What should I do first after a rejection?
Read the message carefully, fix the exact issue, and reply in App Store Connect with what you changed. Do not just resubmit the same build.
Can I appeal a rejection?
Yes. You can reply to the reviewer, and you can ask for a call or submit an appeal to the App Review Board if you think the decision is wrong.
Is a webview app always rejected?
Not always, but an app that is only a website in a wrapper often is. Adding real native features and a real purpose as an app greatly improves the odds.
Can you handle the rejection for me?
Yes, our app submission service includes rounds of fixes and resubmission.
Building apps for clients? Resell Appily under your own brand
Unlimited apps, your logo and your pricing, with our team handling the app store submissions. $85 a month, price locked for as long as you stay subscribed.
0px 0px -6% 0pxDone. Your app is open in the editor.Describe the business…Planning the app…Choosing pages…Building the app…Book classesOrder foodGet rewardsApple Developer accountApp icon 1024 x 1024Screenshots for every sizePrivacy policy URLTest account for reviewGuideline 4.2: Minimum functionalityYour app is a web view of a website.Fix foundAdd native features and resubmit with review notes.Mobile friendlyNative featuresReview riskBuilt with LovableWeb app onlyNeeds push and loginReview risk: high. Native layer needed.A yoga studio in Austin with class bookings, a small shop and reminders for members.Book your next classStudioFitness and wellnessClassesShopOffersRemindersAboutContactA taco truck with online ordering, daily specials and a loyalty card.Order tonight's specialRestaurantFood and drinkOrderSpecialsLoyaltyLocationsAlertsA church with sermons, events, prayer requests and a radio stream.Join us this SundayCommunityChurchSermonsEventsRadioPrayerGive
Google Play phone (1080 x 1920)ScreenshotAdd at least one screenshot first.Android roundAndroid squarePlease choose a PNG, JPG or WebP image.The image is not square, so it is cropped to the centre.The image is smaller than 1024 x 1024, so the largest icon is upscaled. Use a bigger source for the sharpest result.The image has transparency. Apple rejects icons with transparency, so the iOS icons are flattened on the background colour below.Looks good: square and large enough.Apple accountEnrol in the Apple Developer ProgramCosts $99 a year. Organisations also need a D-U-N-S number, which can take days to arrive.Turn on two-factor authentication for your Apple IDRequired to sign in to App Store Connect.Create the app record in App Store ConnectChoose the name, language, bundle ID and SKU. The bundle ID cannot be changed later.Accept agreements and add tax and banking detailsOnly needed for paid apps and in-app purchases, but do it early.The buildApp icon 1024 x 1024 with no transparencyApple rejects icons with an alpha channel or rounded corners already applied.Test on a real iPhoneCheck every screen, login, push notifications and what happens with no internet.No crashes, placeholder text or broken linksGuideline 2.1. The most common reason for a first rejection.More than a website in an appGuideline 4.2. Add real native features such as push notifications, offline content or device features.In-app account deletion if users can create accountsRequired by guideline 5.1.1(v). Deleting the account has to be possible inside the app.Permission texts explain why you need each permissionCamera, location, photos and notifications each need a clear reason.The listingApp name (30 characters) and subtitle (30 characters)Use the real name. Do not stuff keywords in the name.Keywords (100 characters, comma separated, no spaces)Do not repeat words from your name and subtitle.Screenshots for the required device sizesCurrently the 6.9 inch iPhone set is required, and iPad if the app supports iPad. See our screenshot generator.Description, promotional text and what is newDescribe what the app really does. Do not mention other platforms.Support URL and privacy policy URLBoth must open a working page.Age rating questionnaire and categoryAnswer honestly. A wrong age rating can cause a rejection.App Privacy details (the privacy nutrition label)List every kind of data the app or its services collect.Review notes and a demo accountGive a working test login. Explain features that are hard to find.Export compliance (encryption) questionMost apps that only use standard HTTPS answer that they use exempt encryption.Google Play accountCreate a Google Play Console developer accountOne-time $25 fee. Identity verification is required and can take a few days.Closed testing requirement for new personal accountsPersonal accounts created after November 2023 have to run a closed test with at least 12 testers for 14 days before applying for production. Check Google's current rules.Create the app and choose the package nameThe package name cannot be changed after you publish.Signed Android App Bundle (.aab) with Play App SigningPlay requires app bundles for new apps.Target API level meets Google's current requirementGoogle raises the minimum every year.Test on a real Android phoneCheck different screen sizes and Android versions if you can.Account deletion option if users can create accountsGoogle requires an in-app path and a web link.Title (30 characters), short description (80) and full description (4000)No keyword stuffing, no emoji spam and no misleading claims.App icon 512 x 512 and feature graphic 1024 x 500Both are required.At least 2 phone screenshotsUp to 8. Add tablet screenshots if the app supports tablets.Data safety formIt has to match what the app really does and what your privacy policy says.Content rating questionnaire and target audienceRequired for every app.Privacy policy URLMust open a public page.App access instructionsProvide test credentials if parts of the app need a login.Apple App Store:Google Play:App CompletenessApple found a crash, a bug, a broken link, placeholder content, or could not use the app during review.Reviewers test on real devices with a clean install. If the login does not work or the server is down, they reject. Unfinished screens and test text are another common cause.Test on a real device from a fresh installFill in the demo account fields in App Store Connect and check the login worksMake sure your backend is online during reviewRemove every placeholder, lorem ipsum and empty screenAI-built apps often have untested screens and missing demo accounts.Accurate MetadataYour screenshots, description or name do not match what the app really does, or the metadata breaks Apple's rules.Common triggers are screenshots that show features the app does not have, keywords in the name, mentions of Android, and prices or promotions in the wrong fields.Use real screenshots from the final buildRemove other platform names and competitor namesKeep the name to the real brand nameMake the description match the appGenerated screenshots with fake features are a frequent cause.In-App PurchaseThe app sells digital content or features without using Apple's in-app purchase, or links out to a payment page in a way Apple does not allow.Digital goods and subscriptions that unlock features inside the app generally need in-app purchase. Physical goods and real-world services do not. Rules about external payment links differ by region and change, so check Apple's current guidelines.Decide if what you sell is digital or physicalUse in-app purchase for digital featuresRemove buttons that send users to outside payment pages unless your region allows itExplain your payment model in the review notesApps that took payments through a web checkout inside a wrapper hit this often.DesignThe interface looks unfinished, is confusing, or does not follow Apple's design guidelines.Reviewers expect a clean, usable interface that works on all supported screen sizes.Check every screen on small and large iPhonesFix cut-off text and overlapping elementsMake buttons large enough to tapSupport the safe areas around the notch and home indicatorWeb layouts that were not designed for phones can look wrong inside an app.Minimum FunctionalityThe app is too much like a website, a repackaged web page or a simple link collection and does not offer enough lasting value as an app.This is the best-known rejection for wrappers and app-builder output. Apple wants apps that use the platform: push notifications, offline content, device features, native navigation and features that work better than a website.Add real native features: push notifications, offline content, camera or location where it makes senseUse native navigation (a tab bar) instead of a single scrolling web pageMake sure the app works well without the website being open in a browserExplain the native features in the review notes with exact steps to find themThis is the number one risk for apps from Lovable, Base44, Bolt web projects and other web-only builders.Template and app generation servicesThe app looks like it was created from a commercial template or app generation service and was not submitted by the owner of the content.Apple does not accept apps made from a template or app generator unless they are submitted directly by the content owner. Each business needs its own developer account and app.Submit under the client's own Apple Developer accountGive each app its own bundle ID, name and contentDo not publish the same app for several clients under one accountResellers: this is why Appily apps are submitted under each client's own developer account.Spam and duplicate appsApple considers the app a copy of another app, or one of several near-identical apps.Several apps with the same features and a different name or colour are treated as spam.Make each app clearly different in content and purposeCombine near-identical apps into oneDo not submit several bundle IDs for the same appMaking many similar apps from one AI prompt can trigger this.Login servicesThe app offers third-party login such as Google or Facebook without an equivalent privacy-focused option.Apps that use third-party login generally have to offer another login option that limits data collection, such as Sign in with Apple.Add Sign in with Apple, or use plain email and password onlyCheck Apple's current wording for exceptionsSocial login added by an AI builder is a typical cause.Data collection and privacyThe app collects data without a privacy policy, asks for permissions it does not need, or does not let users delete their account.You need a privacy policy link, clear permission texts, and an in-app way to delete the account if users can create one.Add a privacy policy URL in the listing and inside the appWrite clear purpose strings for every permissionAdd a Delete account option in the appOnly ask for the permissions you really useAccount deletion is often missing in generated apps.User-generated contentThe app lets users post content without ways to report, block and moderate it.Apps with social walls, comments or chat need content filtering, a report button, blocking, and published contact details.Add a report option on posts and commentsAdd a way to block abusive usersModerate content and respond to reports quicklyShow contact information in the appRelevant for any app with a social wall, forum or chat.Intellectual propertyThe app or listing uses logos, names or content you do not have permission to use.Using a brand name, a famous character or someone else's content without a licence is rejected.Use only your own brand and contentRemove third-party logos and namesProvide proof of permission if you use licensed contentDeveloper informationApple could not reach you, or the support page does not work.The support URL and contact details have to be real and reachable.Use a support URL that opens a real pageKeep your contact email active during reviewData safetyData safety form mismatchThe Data safety form does not match what the app really collects or what the privacy policy says.Google compares your declaration with the app's behaviour and your privacy policy.Review every SDK and service the app usesUpdate the Data safety form after every changeMake sure the privacy policy matchesGenerated apps often include analytics and auth services that must be declared.Target APITarget API level too lowThe app targets an Android API level older than Google's current requirement.Google raises the required target API every year. Older targets cannot be published or updated.Update the target SDK in your build settingsRebuild and test on a recent Android versionWebviewWebview spam and minimum functionalityThe app is mostly a webview of a website, or of a site you do not own.Google does not allow apps whose main purpose is to show a website you have no permission to use, or that add no value of their own.Make sure you own the website or have written permissionAdd features that go beyond the websiteDescribe the app honestly in the listingWrapped AI-built web apps can fall into this.Closed testingClosed testing requirementYou applied for production access without finishing the required closed test.Personal developer accounts created after November 2023 need a closed test with at least 12 testers opted in for 14 days. Check Google's current rules.Recruit at least 12 testersKeep them opted in for 14 days in a rowApply for production access after the testPermissionsSensitive permissionsThe app requests permissions such as background location, SMS or all-files access without a valid reason or declaration.Sensitive permissions need a declaration form and a clear core use.Remove permissions you do not needComplete the permission declaration if you must keep onePaymentsPayments policyDigital goods are sold without Google Play billing.Digital goods and subscriptions in apps generally have to use Google Play's billing system, with exceptions that depend on region and category.Use Google Play billing for digital featuresCheck Google's current payments policyApple App StoreGoogle PlayWhat it meansWhy it happensHow to fix itAI-built and builder apps:No match. Try a guideline number such as 4.2, or words like privacy, login or crash.Your site already works on phones.Make the site fully mobile friendly first. A web view only shows what the site looks like on a phone.The site is not mobile friendly. Fix that before you put it in an app.HTTPS is on.Move the site to HTTPS. Apps and stores expect secure connections.You need the owner's permission to put a site in an app. Both stores check this.Shops and booking sites gain a lot from an app, with push notifications and loyalty.A brochure site or blog on its own is the classic Apple 4.2 rejection. Add native pages and features around it.Web apps need native features around them, such as push notifications and native navigation.You planChoose at least two or three native features such as push notifications, loyalty or booking.Add one or two more native features to make the app clearly more than a website.If users create accounts, add in-app account deletion and a privacy policy. Both stores require it.High review riskMedium review riskLow review riskPush notificationsLoyalty cardBookingCatalog and shopMember accountsQR code scannerNews wallAudio and radioReadinessWhat to doHow Appily helpsTheLinks featureNative features keep working even if your website is down.Build it with AppilyAlready built? We submit it for youLovableBoltReplitBase44BubbleGlideAdaloRorkCursor, Claude Code or another toolIt is a web app. Apple rejects apps that are mostly a website in a wrapper (guideline 4.2).An exported web project still has to be packaged as a real app with native features around it.A React Native or Expo project can be a real native app, but it still has to meet the store rules.There are no native features. Add push notifications, offline content or device features.Accounts need in-app account deletion and a privacy policy (guideline 5.1.1).User content needs reporting, blocking and moderation (guideline 1.2).Digital purchases have to follow Apple's and Google's billing rules.You need a public privacy policy page. Both stores require the link.Create your Apple Developer account ($99 a year) and Google Play account ($25 one time). Our submission service can guide you.High risk of rejectionMedium risk of rejectionLow risk, if the details are rightRead our guide forRun theWhyNothing obvious stands out.Next stepsGet it published for $49Build natively with the Appily AI App BuilderThis is a guide, not a guarantee. Apple and Google decide every review.Remove the spaces after commas in the keyword field. They waste your 100 characters.These keywords already appear in your name or subtitle, so you can drop them:Repeated keywords:No problems found.Your app nameYour subtitleYour short descriptionWeb addressTextAny textNetwork namePasswordSecurity (WPA, WEP or nopass)Email addressSubjectPhone numberType something to create a QR code.That is too long for a QR code. Shorten it.
