Removed from sale is a message you have to answer, and the clock started when it arrived.
An app leaves a store in one of three ways. You took it down yourself, the store took it down over a policy or legal problem, or the store took it down because nobody has touched it in years. Each one has a different route back, and the route starts with reading the notice rather than the listing. Apple sends it as a message from App Review inside App Store Connect. Google sends an email and repeats it on the Policy status page in Play Console. One thing to clear up before anything else: Removed from Sale is not an App Store Connect app status any more. Apple retired that label, along with Developer Removed from Sale, in its release notes dated 8 February 2024, and told developers to check Pricing and Availability instead. If you are hunting that phrase on a screen, you will not find it.
Everything below comes from Apple's and Google's own help pages, read on 16 October 2026. The guidelines a removal message cites are the same ones behind why apps get rejected, so the wording will look familiar if you have been through review. What is different is the clock, the effect on people who already have the app, and the fact that you get exactly one appeal.
Start hereThe short version
Three removals wear the same word, and only one is about a broken rule.
The first kind you did yourself. In App Store Connect that is Pricing and Availability, scroll to the bottom, Remove App From Sale. It takes up to 24 hours, it needs the Account Holder, Admin or App Manager role, and it is not held against you. People who already downloaded the app keep getting updates, and they can redownload it from their purchase history for as long as the necessary contract stays active.
The second kind is enforcement. App Review confirms a problem with a version that is already live, and you get a message naming the issue and the rules it breaks. A milder issue may come with 14 days to fix it. A safety or legal problem may be removed on the spot. A concept Apple considers fundamentally incompatible is removed and cannot be restored at all. On Google Play the same tier splits differently, into a warning with a day count in it, then a removal, then a suspension that puts a strike on the account.
The third kind is neglect. Apple runs a process called App Store Improvements for apps that have not been updated in three years and also fail a minimal download threshold. You get a message asking for an update within 90 days. Nothing is wrong with the code. It is just old and nobody is installing it, which is the least dramatic and most common way a working app disappears.
What does Apple do when it removes a live app?
Apple names three grounds for pulling a published app: failing to follow the App Review Guidelines, failing to follow the Apple Developer Program License Agreement, or breaking applicable law. It also names the situations that surface them, and none of them is a fresh submission. An app that hides features or was changed after approval, including by a server-side change that introduces a violation. Users reporting a problem that did not show up during review. A legal, intellectual property or government takedown request. In other words, a removal usually comes from something that happened after the app was approved.
The notice is specific and it lands in one place. Apple says that if App Review confirms an issue with a live version of your app, you will receive a message in App Store Connect describing the issue and the rules that were violated. There is no email-only path to worry about and no status to interpret. Read the message, because the severity grade inside it decides everything that follows. Less severe issues may be given 14 days to resolve, and the app is only removed if App Review does not receive a compliant update submission inside that resolution window. Serious issues, which Apple illustrates with safety and legal concerns, may be removed immediately, and then you must submit a compliant update to restore the app.
One grade has no route back. Apple says apps with a fundamentally incompatible concept, its example being an app designed to deliver objectionable content, are removed immediately and cannot be restored, and that the developer must submit a new app with a compatible concept. If your notice uses that language, stop writing the fix. Nothing you ship to that app record will bring it back.
The quietest removal has nothing to do with rules. Under App Store Improvements, Apple messages developers whose apps have not been updated within the last three years and which also fail a minimal download threshold, meaning the app has not been downloaded at all or extremely few times during a rolling 12 month period. The ask is an update within 90 days. Miss it and the app comes off until you submit an update and it is approved, with no deadline on when you do that so long as your membership is active. Apps that crash on launch skip the window and are removed immediately. That is the unglamorous argument for budgeting what an app costs to maintain rather than treating launch as the finish line.
Apple, App Review Help, respond to an app removal, read 16 October 2026
Read the message, then pick one
Which removal is this?
Most of these eight have a route back to the same listing. Two do not. The wording of the notice is what tells them apart, so start there rather than with the store page.
What it is
App Review confirmed an issue with a version that is already on the store. The message names the issue and the rules it breaks.
How long you have
Apple says apps with less severe issues may be given 14 days to resolve the issue.
The route back
Submit a compliant update inside that window and the app is never removed. Miss it and it comes off.
Taken from Apple and Google help pages read on 16 October 2026. Your own notice overrides any of it.
How is a Google Play removal different from a suspension?
Google uses four words and they are not interchangeable. A rejection stops a new app or an update from being published, and your last successfully published version stays on Google Play. A removal takes the published version, and previous versions of that app, off the store until a compliant update is submitted. A suspension takes the app off and counts as a strike against the good standing of your developer account. A termination removes every app in your catalogue. Google is explicit that a single removal does not immediately affect your account standing, and equally explicit that multiple removals may lead to suspension.
The real difference between a removal and a suspension is what you keep. Google says your users, statistics and ratings are retained once you submit a compliant update for a removed app. Once the app is suspended, you forfeit the users, statistics and ratings of that app. A removal is therefore a delay. A suspension is a reset of everything you built up on that listing, which is the practical reason to treat the first removal email as urgent rather than as a formality.
There is also a tier above all of this that is easy to miss, because it does not remove anything yet. Google sends warnings, which it says do not affect your account standing, and the app is removed after the number of days found in the initial warning email. That number is in the email and nowhere else, so the email is the document, not the console. Checking where you stand means opening the app in Play Console and selecting Policy status from the left menu, which is also where an Appeal option appears once the app is suspended.
When the compliant update is ready, do not ship it to everyone at once. The release that fixed one policy problem is exactly the kind of hurried build that introduces another, and a staged rollout on Google Play keeps a second mistake away from the whole install base while you watch the crash rate. Google also notes that users of a removed or suspended app may receive a push notification from Google Play Protect telling them about the change, so assume your customers find out before you have finished writing to them.
Google, Play Console Help, my app has been removed from Google Play, read 16 October 2026
How do you appeal, and how many chances do you get?
One chance, on both stores. That is the single most useful fact here, and it changes the order of operations. Google says you may submit one appeal per app removal, suspension, or other enforcement action. Apple says only one appeal per rejected or removed app, and that if the message cites several violations you have to address all of them inside that one appeal. So do not file on the day the message arrives. Collect the facts, then write once.
Apple puts a cheaper step in front of the appeal, and it is the one most people skip. Before filing, reply to the rejection, removal or termination message you received in App Store Connect and explain the issue. Only if that is not enough do you go to the Submit an appeal to App Review form and take it to the App Review Board. For a removal, Apple asks you to point at the specific requirements involved and explain how your app satisfies them, which means quoting the guideline number and answering it line by line. The Board replies with a message in App Store Connect when the investigation is complete, and may ask for more information or schedule a call. The form takes up to five rejected or removed apps at a time. Apple also says what the Board is not for: reinstating an account that is already terminated, chasing a status update, or asking for an expedited review.
Deadlines are where the two stores genuinely differ, and where a common piece of advice is wrong. Apple publishes no deadline for appealing an app removal. Google publishes one, but it covers account terminations only: since 28 January 2026 you must appeal within 180 days of the date your account was terminated, after which Google considers the matter closed and the option to appeal is no longer available. There is a small mercy attached. Appeal late in that window and you automatically get an extra 30 days after the decision to reply with new information for re-review. No equivalent clock is published for an app removal or a suspension, so do not assume you have 180 days for one of those.
Two practical notes before you write. Google can only respond to appeals in Chinese, English, Japanese and Korean at this time, even though the removal email may arrive in your app's default language. And the enforcement action stays in effect unless the appeal is granted, so an appeal is not a stay of execution. If a fix exists, ship the fix and appeal only the part you think was wrong.
Google, Play Console Help, one appeal per enforcement action, read 16 October 2026
What happens to the people who already have the app?
Less than you fear, in the cases Apple actually documents. If you removed the app yourself, App Store Connect Help says users who previously downloaded it from the App Store in that country or region will continue to receive app updates, and that the app can be redownloaded from a customer's purchase history as long as the necessary contract remains active. For an App Store Improvements removal, Apple is more explicit still: the app remains fully functional for current users, they experience no service interruption, and they can continue to make in-app purchases. The removal is about discovery. It is not a remote kill switch.
Two honest gaps. Apple does not publish the same reassurance for an enforcement removal, so do not promise your customers anything about one. And the contract clause matters more than it reads: if the agreement behind the app lapses, the redownload path goes with it, which is a reason not to let a membership expire while an app is off the store waiting for you.
Google answers the same question from the other end. A removal is survivable for your numbers, because users, statistics and ratings are retained once you submit a compliant update. A suspension is not, because you forfeit them. Separately, Google Play Protect may push a notification to people who have the app, which is why your own message to customers should go out the same day rather than after the appeal.
If you sell subscriptions, the removal exposes where your billing actually lives. Apple says in-app purchases keep working for current users through an App Store Improvements removal, which is good news only for the store-billed part of your revenue. Anything you bill outside the app, and the receipt plumbing that tells your server who is entitled to what, is a separate decision about which payment layer to use, and it is much easier to make before a takedown than during one.
Apple, App Review Help, app removals and App Store Improvements, read 16 October 2026
The same word, two different enforcement systems
| What you want to know | App Store | Google Play | Same on both |
|---|---|---|---|
| Where the notice arrives | A message from App Review in App Store Connect | Email, plus the Policy status page in Play Console | No |
| Grace period before it goes | Up to 14 days for a less severe issue, none for a serious one | The number of days named in the initial warning email | No |
| The route back on the shelf | Submit a compliant update | Submit a compliant update | Yes |
| Installs and ratings afterwards | Current users keep a working app | Retained after a removal, forfeited after a suspension | No |
| Appeals you are allowed | One per rejected or removed app | One per removal, suspension or other enforcement action | Yes |
| A published deadline to appeal | None for an app removal | 180 days, but only for account terminations | No |
Where this lands if a builder generated your app
The removal message comes to you, and so does the fix. App Store Review Guideline 4.2.6 is the reason: apps created from a commercialized template or an app generation service are rejected unless they are submitted directly by the provider of the app's content. That is you. It follows that the App Store Connect message, the 14 day window and the one appeal are all yours to handle, whoever or whatever wrote the code.
Newly is an AI app builder, and the part that matters when a store pulls your app is ownership. You describe the app and it generates a real React Native and Expo project that you own, with two-way GitHub sync, so the code behind a removed listing is sitting in your own repository rather than inside a vendor's account. It uploads iOS builds to TestFlight, publishes to Google Play internal testing and builds a standalone Android APK. It does not submit to the App Store for you, because Apple requires the content owner to submit. Newly costs $25 a month, with no free tier.
In practice that means a compliant update is a code change and a resubmission, on your schedule, not a support ticket in a queue. The honest limit is the same one every tool has: nothing can appeal for you, nothing can shorten Apple's review of an appeal, and no builder can restore an app whose concept Apple has ruled out. What a builder can do is make the second attempt cheap enough that you make it this week.
Questions people ask when an app comes off the store
No. Apple retired it. The App Store Connect release notes dated 8 February 2024 say that Developer Removed from Sale, Removed from Sale and Pending Agreement are no longer app statuses, and that Ready for Sale was renamed Ready for Distribution, which now only means the app can be published. To see whether your app is actually on the App Store, open Pricing and Availability. The per country statuses you may find there include Not Available, Processing to Not Available and Cannot Sell App, and Apple says to hold the pointer over Cannot Sell App to see the reason.
Read the notice, ship the fix, keep the appeal in reserve
Most removals end with a compliant update rather than an argument. The sooner you can build and submit that update yourself, the less any of the above costs you.
Start building