Broken functionality is the Google Play policy a rejection cites when the reviewer’s copy of your app would not install, would not load, or loaded and stopped responding. The notice sits in Play Console under Policy status, and a rejected update leaves your last published version live while you fix the cause and resubmit.
What broken functionality means in a Google Play rejection
A broken functionality rejection means the review could not use the app as submitted. Google’s policy gives three examples of common violations: an app that does not install, one that installs but does not load, and one that loads but is not responsive. The fix usually belongs in the build, not in the store listing.
Everything before the notice, from the developer account to production access, is laid out in the first Google Play release, step by step. What follows starts once a notice has arrived.
The meaning of broken functionality fits in one line of Google’s Functionality, Content, and User Experience policy: “We don’t allow apps that crash, force close, freeze, or otherwise function abnormally.” One notice a developer shared on a forum in 2024 was headed “Issue found: Violation of Broken Functionality policy” and named the example underneath it, “App installs, but doesn’t load”. The rule belongs to Google Play, so broken functionality only ever concerns the Android build you uploaded there; Apple reviews the iPhone version against its own guidelines.
| Google’s example of a violation | What it can look like in an AI-built app | The first check |
|---|---|---|
| Apps that don’t install | A build made for a processor type or a minimum Android version the review device does not have | Install the exact file you uploaded on a phone that has never run the app |
| Apps that install, but don’t load | A blank first screen while data loads, an API key missing from the release build, or a region or network block that keeps the reviewer from the content | Open that install signed out, on mobile data, and wait on the first screen without touching it |
| Apps that load, but are not responsive | A tab that opens a placeholder, a slow first load with no loading state that looks frozen, or a sign-in wall with no working test account | Tap every tab and button on the first three screens with the account you gave the review |
The left column is Google’s wording. The middle column is how we’d expect those examples to show up in an app a prompt generated, and the right column is where we’d start; neither is on Google’s page.
A similar name belongs to an API security flaw, Broken Function Level Authorization (OWASP API5:2023), which has nothing to do with this store policy. And if the build passed review and users’ phones began crashing afterwards, that is a crash after the store accepted the build, a separate investigation with its own tools.
Rejected, removed or suspended: what the Play Console notice means
The word in the Play Console notice decides what stays live. A rejected update leaves the last published version on Google Play, a removed app stays off until a compliant update is submitted, and a suspended app is no longer available on Google Play.
To see the policy status in Play Console, open Play Console, select the app and choose Policy status on the left menu, the route Google gives on its Check your app’s policy status page.
| The word in the notice | What Google’s page says | What it costs you now |
|---|---|---|
| Rejected | ”If your app was rejected, the last version that you successfully published is still available on Google Play.” | The update waits; installs, statistics and ratings stay, and the developer account’s standing is untouched |
| Removed | ”If your app was removed, it won’t be available on Google Play until a compliant update is submitted.” | The listing is hidden from users; users, statistics and ratings are retained once you submit a compliant update |
| Suspended | ”If your app was suspended, it’s no longer available on Google Play.” | A strike against the developer account, and the app’s users, statistics and ratings are forfeited |
| Account terminated | ”When your developer account is terminated, all apps in your catalog will be removed from Google Play and you will no longer be able to publish new apps.” | Every app on the account goes, and related Google Play developer accounts are permanently suspended |
Four rows are not the whole list. Google’s Enforcement Process page also names Limited Visibility, Limited Regions, Restricted Developer Account and Dormant Accounts. One line on the policy status page governs everything after the notice: “Until a policy violation has been fixed, don’t republish a rejected or removed app.”
Our reading of the two pages: for a first issue, the word tends to follow what happened to the listing, so an update blocked in review is rejected and a live version caught later is removed. Google adds that suspension can follow “egregious or multiple policy violations, as well as repeated app rejections or removals.”
If the notice says removed or suspended, or the same policy has come back on a second submission, stop resubmitting and get help: start with a free audit, a 30-minute video call where we talk through with you why the policy keeps returning and what that says about how the app was built. In our Production Hardening Sprint, we automate smoke tests for signup, login, the core product action, and payment flows.
Four things that look like a rejection and are not
| What you saw | What it is | Where the answer lives |
|---|---|---|
| An upload refused because the bundle is signed with another key | A key check: Google uses the upload key to verify your identity, and can reset a lost one | Play App Signing (Protected with Play, Play Store protection, Manage Play app signing) |
| A warning that the app’s target API level is too low | A distribution rule: from August 31, 2026, new apps and updates must target Android 16 (API level 36) or higher to be submitted | The targetSdkVersion in the app’s manifest |
| An icon or feature graphic error on the store listing | A file outside the stated requirements: the icon is a 32-bit PNG at 512px by 512px, up to 1024KB; the feature graphic is 1024px by 500px | Main store listing (Grow users, Store presence, Main store listing) |
| No production access after a closed test | The testing requirement for personal accounts created after November 13, 2023: at least 12 testers opted in continuously for at least 14 days before you apply | The Dashboard in Play Console, where the application is made |
An existing app also has to target Android 15 (API level 35) or higher to stay available to new users on devices running a newer Android version than its target. When production access is held back, Google may ask you to keep the closed test running, for example with fewer than 12 opted-in testers or too little tester engagement. None of the four names a policy, so in our view an appeal will not move any of them; the fix sits in the key, the manifest, the image or the test. The first row has its own walkthrough for apps built in Base44: an upload refused for a changed signing key.
Google Play rejection reasons, and the policy behind each
Each reason has its own Google policy page, and the notice names the policy it applied. It may not name everything: Google warns that removal or administrative notices “may not indicate each and every policy violation present in your account, app, or broader app catalog.” On Apple’s side the map runs by guideline number instead: App Store rejections by Apple guideline.
| What the app did | The Google policy that names it | The change that clears it |
|---|---|---|
| Crashed, froze or did not respond | Broken Functionality, in Functionality, Content, and User Experience | The first section of this article: fix the build, then resubmit |
| Had almost nothing in it | Limited Functionality and Content, on the same page | Build the features the listing promises before you submit again |
| Promised in the listing what the build does not do | Metadata | Rewrite the title, icon and description so they describe what the build does |
| Wrapped a website the developer does not own, or repeated an existing app | Spam (Webviews and Affiliate Spam; Repetitive Content) | Get the site owner’s permission, and add content or features of your own |
| Had no privacy policy link, or one that did not load | User Data (Privacy Policy) | A live, public URL in the Play Console field, plus a link or text inside the app |
| Gave no way to delete the account | User Data (Account Deletion Requirement) | An in-app path to deletion and a web link where users can request it |
| Asked for permissions no promoted feature uses | Permissions and APIs that Access Sensitive Information | Remove every permission no current, promoted feature needs |
| Generated content with AI and gave no in-app way to report it | AI-Generated Content | An in-app report or flag control that works without leaving the app |
| Could not be signed into by the review | Sign-in details on the App content page (Prepare your app for review) | Working sign-in details entered in App content |
Data safety answers that do not match the app are a cause of their own. Google puts the duty on the developer, “You alone are responsible for making complete and accurate declarations”, and says that when it becomes aware of a discrepancy between the app’s behavior and the declaration, it may take appropriate action, including enforcement action. Filling in that form is part of the first release, before any notice arrives.
The six below are the ones we’d check first on an AI-built app. The order is our judgment, not Google’s.
The review could not sign in: sign-in details in App content
Google’s rule: if your app or parts of it are restricted by login credentials or other authentication, “you must provide all required details to enable access to your app.” The details go on the App content page (Policy and programs, then App content), under Sign-in details, as Prepare your app for review shows. This is where the reviewer test credentials and app access instructions go. Create the account fresh, sign in with it on a device that has never had the app, and only then enter it. A one-time password, multi-factor authentication or a login with more than two fields gets a note in the “Any other instructions” field.
The privacy policy link is missing or does not load
Under the User Data policy, “All apps must post a privacy policy link in the designated field within Play Console, and a privacy policy link or text within the app itself.” The URL has to be active, publicly accessible and not geofenced, with no PDFs, so open it signed out in a private browser window before you submit. What the policy itself has to say, checked against what the app really does, is the subject of a privacy policy that matches the app.
No way to delete the account from inside the app
If the app lets people create an account, Google’s account deletion requirements ask for two routes: “an in-app path to delete their app accounts and associated data” and “a web link resource where users can request app account deletion and associated data deletion.” Freezing or deactivating the account “does not qualify as account deletion.” A delete button that removes only the profile row falls short of that. Building deletion that meets Google Play’s account deletion requirement, records and files included, is its own job.
Permissions the listing does not explain
The permissions policy allows only permissions “that are necessary to implement current features or services in your app that are promoted in your Google Play listing.” A generated app can keep permissions for a feature someone asked about once and later dropped, so read the manifest’s list against the listing. Start with camera, location and contacts. On contacts, Google has announced a Contacts Permissions policy, effective January 27, 2027, under which apps that don’t need broad access must use the Android Contact Picker.
Too little app, or a website in a native shell
Limited Functionality and Content covers apps that are static, “for example, text only or PDF file apps”, and apps “designed to do nothing or have no function.” The Spam policy rules out apps whose primary purpose is to “provide a webview of a website without permission from the website owner or administrator.” A generated shell whose tabs open placeholders can trip both at once. What a wrapped web app has to add before a store takes it is covered in publishing a web app in a native shell.
AI-generated content with no way to report it
The AI-Generated Content policy says apps that generate content using AI “must contain in-app user reporting or flagging features that allow users to report or flag offensive content to developers without needing to exit the app.” Its examples are chatbots where the conversation is a central feature, and images or video generated from text, image or voice prompts. As we see it, a generated chat screen tends to ship a message list and a send button, and the report control is a moderation feature nobody asked the builder for.
How to fix the cause and resubmit
Fixing a Google Play rejection starts in Policy status, not in the email: read the policy sentence the app failed, reproduce it on a clean device with the exact build and sign-in details you submitted, fix every screen with the same cause, then upload the compliant bundle and deactivate the old one on every track.
The steps are the same whatever the policy. For how to fix broken functionality in particular, step 3 does most of the work, because the reviewer’s failure has to be seen before it can be fixed.
- 01 Open Play Console, select the app and read Policy status for the name of the policy.
- 02 Open that policy page and find the sentence the app failed.
- 03 Reproduce it: install the exact build you submitted on a device that has never run the app, sign in with the details you entered, and reach the screen the policy points at.
- 04 Fix the cause, not the one screen: if one generated screen breaks on an empty state, check every generated screen for the same gap.
- 05 Read the pre-launch report for crashes on the devices Google ran the build on.
- 06 Update every release type, internal, closed and open testing included, upload the compliant bundle across all tracks and deactivate the non-compliant bundles.
- 07 Appeal only if the enforcement itself was wrong, and attach a screen recording of a clean install, the sign-in and the main screens.
The pre-launch report is the closest thing to real device testing that Play Console runs for you: after an upload it installs the build on a set of Android devices in Google’s test lab and crawls it for several minutes, typing, tapping and swiping, subject to the lab’s capacity. It reports stability, Android compatibility, performance and accessibility issues, and the crawler can use the sign-in details already on the App content page.
Step 6 has a trap in it. Google’s page for an app removed from Google Play warns that if you fail to deactivate the non-compliant bundles, “your attempt to resubmit your app will fail, and live versions of your app bundle(s) may be removed from Google Play.” The same page allows one appeal per app removal, suspension or other enforcement action and answers appeals only in Chinese, English, Japanese and Korean, so an appeal is worth spending only on a decision that was wrong.
Once the fix is in, how long Google Play review takes sets the wait. Apple runs a different process, covered in appealing on Apple’s side, and we’d write a Play appeal from scratch rather than reuse a reply written for Apple.
How to stop the next rejection: checks before every release
Three checks before every upload cover the causes above: a fresh install that walks sign-up, login and the main action on a real device, an account deletion that works from inside the app, and a privacy policy that says what the app actually sends and to whom.
We audited 21 third-party apps in June and July 2026, and at least 18 of them had no working test anywhere: 17 had none at all, and a retail POS had a checkout “test suite” that never executed the actual checkout code. Those apps were picked for audit rather than drawn at random, so the count describes that group, not AI-built apps as a whole. Our take: in an app with no test at all, the store reviewer may be the first person to walk sign-up on a clean device.
| Check | What it catches | The evidence to keep |
|---|---|---|
| A fresh install on a real device that walks sign-up, login and the main action | Broken Functionality, and sign-in details that do not work | A screen recording and the build number |
| An account deleted from inside the app, then a sign-in attempt with that same account | The account deletion requirement | The sign-in error the deleted account gets |
| The privacy policy read beside a list of every service the app sends data to | User Data and Data safety mismatches | That list, dated |
The first check grows into a suite that runs on every change: end-to-end smoke tests for signup, login and payments keep a later edit from breaking sign-up without anyone noticing. The wider set of code health controls sits under engineering standards for AI-assisted teams.
Each check has a counterpart deliverable in the sprint, aimed at the app behind the store build, with its own verify step. Critical-path smoke tests (deliverable 10.5) are verified by running the suite in CI and demonstrating that an intentional regression fails it. For complete account deletion (1.8), we delete a seeded account and inspect its related records, files, and recorded retention exceptions. Privacy and terms alignment (12.3) is verified by comparing the policy statements with the data inventory and provider flows and recording the owner-approved alignment. None of the 123 deliverables tests a native mobile app package on a device, so testing the store build itself stays with whoever builds it.
Common questions about Google Play app review
Why was my Google Play app rejected?
Google Play rejected the app because its review found at least one compliance issue with its policies, and Play Console shows which one under Policy status. Google also says its notices may not list every violation in the app, so check the rest of it before you resubmit. In apps built with AI, we’d look first at Broken Functionality, sign-in details, the privacy policy link and account deletion.
Where can I find the privacy policy in the Google Play Console?
The privacy policy field is on the App content page in Play Console (Policy and programs, then App content): under Privacy Policy, select Start, or Manage if one is already there, and enter the URL. Google also requires a privacy policy link or text inside the app, and the policy itself must sit at a URL that is active, public and not geofenced.
How to contact Google developer support?
For a rejection, removal or suspension, Google’s route is a troubleshooter called “Contact Google Play about an account termination, app removal, or suspension”, which asks, among other things, whether you believe the app was rejected, removed or suspended in error. The troubleshooter also notes that you can now request help from the Help page in your Play Console account. Each removal, suspension or other enforcement action gets one appeal. For missing sign-in details, Google says you can update them and send the app for review again without contacting or waiting for a reply from the policy support team.
When is it time to get outside help with repeated Google Play rejections?
Outside help is worth it when the same policy returns on a second submission, when the notice says removed or suspended, or when nobody can say what the app sends to whom for the Data safety and privacy answers. AxonBuild can weigh up with you on a free audit whether the repeat is one bug or a pattern in how the app was built, a 30-minute video call with no code access needed.
Did Google Play turn your app away?
A rejection names a policy, but the change it asks for can sit in your privacy page, your permissions or how the app behaves. During the audit, we go over the notice and your app with you, name the likely cause, and tell you what to change before you resubmit.
Book a free audit →
Free · 30 minutes · No code access needed