App removed from the App Store or Google Play — how to get it back

The message from the store usually arrives at the worst possible moment and is only a few sentences long: the app has been removed because it violates a policy, has not been updated, or something is wrong with the account. The first instinct is to publish it again, ideally on a new account. That is usually the worst possible move.

Most removals from the App Store and Google Play can be reversed without losing users, ratings or the package name. The condition: you first need to work out exactly what happened, because "removed", "suspended" and "not visible" are three different situations in the stores, with three different ways back.

The first hour: what not to do

• Do not delete the app from the console or create a new account. Google treats a new account created to get around an enforcement action as a separate policy violation and usually closes it just like the previous one.
• Do not resubmit the same version. Without fixing the cause you will get another rejection, and with policy violations each subsequent decision is harsher.
• Do not shut down the backend. Removing an app from the store does not uninstall it from phones. Existing users keep using it, signing in and paying.

Instead, find the message from the store. On Google Play: the Play Console inbox and the Policy status page for the app. On the App Store: the version status in App Store Connect and the messages from App Review. Also check which address the store emails go to — in projects we take over, it is often the inbox of someone who left the company long ago.

Removed, suspended, not visible — not the same thing

The last row is not a joke. Before you start blaming the store, check the country availability settings and the change history in the console.

The most common causes and what to do about them

An app that has not been updated in a long time (App Store)

As part of its App Store Improvements process, Apple notifies the owners of apps that have not been updated in a long time and do not work properly on current iOS versions or do not meet current guidelines. From the notice, you have 30 days to submit an update for review. Apps that crash on launch can disappear immediately.

If the deadline passes, the app is removed from sale but stays on the account: it comes back once a new version is approved, with the same listing and ratings. There is one catch — the new version has to be built with the current Xcode and SDK. In a project nobody has touched for two or three years, that means upgrading dependencies and fixing what breaks on new OS versions, not "rebuilding it in ten minutes". That is why 30 days is less time than it sounds.

A store policy violation

The most common reasons we see in older apps:

• no privacy policy, or a link that leads to a page that no longer exists;
• a Data safety declaration on Google Play or App Privacy details on the App Store that do not match what the app actually collects;
• an old version of an advertising or analytics SDK that collects data the declaration does not mention;
• permissions without justification: background location, SMS, access to all files;
• no way to delete the account from within the app;
• payments for digital content outside the store's billing system.

Note the third point: the cause is often a library, not code someone wrote deliberately. The procedure is always similar: read the policy the store quotes carefully, find the cause, fix it, update the declarations and submit an update with a note to the reviewer explaining what changed. We described this in detail in the article on what to do when your app is rejected.

Suspension on Google Play

This is more serious than a removal. A suspended app is removed indefinitely, and the suspension goes on the account's record: several suspensions, or one for an egregious violation, can lead to the account being terminated and every app being removed.

The only way to bring back the same app is an appeal filed from the Policy status page. An appeal makes sense when the decision was wrong — for example, an automated check flagged a legitimate feature as a violation. In that case, be factual: what the app does, why it complies with the specific policy, and evidence (a screen recording, a link to the privacy policy, documentation). Asking for "a second chance" without arguments rarely changes anything.

If the violation was real, Google usually allows the fixed app to be published only under a new package name. That means a new store listing, with no ratings and no automatic update for existing users. You then have to plan a migration: a message in the old version linking to the new one, and preserving user accounts on the backend.

An inactive developer account (Google Play)

Google closes accounts it considers inactive. An account with apps falls into this category when all of the following apply:

• it is more than a year old,
• its apps have fewer than 1,000 combined lifetime installs,
• the email address and phone number are not verified,
• nobody has used Play Console for 180 days.

The owner receives an email with a deadline and reminders 60, 30 and 7 days before it. To prevent closure, verify the contact details in the account details and publish an update — a release on the internal or closed testing track is enough. After the deadline, the account is closed and the registration fee is not refunded. There is usually no good way out of that situation.

This risk mainly affects company apps with a small number of installs: apps for employees, B2B customers or events. Exactly the ones that "just work" and that nobody looks at.

An expired Apple Developer Program membership

Apple Developer Program membership is annual. When it is not renewed — because the company card expired or the person with the Account Holder role left the company — the apps on the account stop being available on the App Store. Only the Account Holder can renew the membership.

After renewal, the apps come back, but the status in App Store Connect can take a while to update and sometimes you need to contact Apple Developer Support. Preventing it is much simpler: automatic renewal, a valid card and an account created on a company Apple ID rather than an employee's personal address. If the account is in the hands of someone who no longer works with you, start with the article on what to do when your developer disappears, or with transferring the app to your own account.

Missing trader status in the EU (App Store)

Since 17 February 2025, Apple has been removing from the App Store in European Union countries the apps of developers who have not provided the trader status required by the Digital Services Act (DSA). A company that earns money from an app — through sales, in-app purchases or advertising — is a trader and must provide an address, phone number and email, which are shown on the app's listing.

The symptom is distinctive: the app is available, say, in the US, but not in Poland or other EU countries. The fix is to complete the details in App Store Connect and wait for verification, which can take longer than the app review itself.

A legal complaint

A trademark or copyright complaint — usually about the name or the icon — can lead to the app being removed in selected countries or everywhere. You respond through the form indicated in the store's message. If the rights are on your side, prepare the documents (trademark registration, the contract with the designer); if not, changing the name or icon is often faster.

How to restore the app: the order of steps

1. Establish the status and the exact cause. The message from the store, the policy it quotes, Policy status in Play Console, the version status in App Store Connect.
2. Check that you have everything needed to ship a release. Owner access to the accounts, the upload key on Android, Apple certificates and profiles, the source code of the version that is in the store. With Play App Signing enabled, a lost upload key can be reset through Play Console.
3. Check that the project builds at all with current tools. In an app that has not been updated for several years, this is usually the largest part of the work.
4. Fix the cause and check the other requirements while you are at it: target API, privacy declarations, account deletion. Otherwise the next review will reject the app for a different reason.
5. Submit the update or the appeal with a note to the reviewer: what changed and which message it responds to.
6. Once the app is back in the store, set up monitoring and make sure the situation does not repeat itself.

Rough timelines:

How to prevent it from happening again

• At least one or two updates a year, even purely technical ones (SDK, targetSdk, Xcode).
• Store emails going to a shared company address that more than one person reads.
• Developer accounts owned by the company, with at least two people holding admin rights.
• Automatic renewal of the Apple membership on a valid company card.
• Verified contact details in Play Console and trader status completed in App Store Connect.
• A yearly review of the privacy declarations and the list of SDKs in the app.
• Signing keys, certificates and credentials in the company password vault, not on one person's laptop.

Summary

An app removed from the App Store or Google Play is usually a problem to fix, not the end of the product. The key is recognising which situation you are dealing with: a removal needs a fixed update, a suspension needs a well-argued appeal, and an expired membership or missing trader status needs a few clicks in the account settings. The most expensive scenarios — a terminated account and a new package name — almost always come from nobody reading the store's messages.

Bringing apps back to the stores is an everyday part of our app reactivation work. If your app has disappeared from the store or you have received a warning with a deadline, start with a free app analysis — we will tell you what the cause is and how much work it takes to bring it back.