Three reasons apps quietly disappear from the App Store

"The app was gone." That is usually how an owner finds out: a customer sends a screenshot of an empty search result, or a link that opens to nothing. There was no dramatic ban. There was an email, months earlier, to an inbox nobody checks.

We keep 17 apps of our own on the App Store and Google Play, and we read Apple's and Google's mail for all of them through a support desk we built for exactly that, after finding store notices piling up in a filtered folder. So we watch this closely. Here are the three reasons an app gets removed from the App Store quietly, what Apple actually says about each, and how to tell which one hit you.

Reason 1: Apple's outdated-app cleanup

Apple runs an ongoing process it calls App Store Improvements. The rule, in Apple's own words on that page: developers of apps that have not been updated within the last three years and fail to meet a minimal download threshold, meaning the app has not been downloaded at all or extremely few times during a rolling 12-month period, receive an email saying the app has been identified for possible removal.

You then have 90 days to submit an update to keep the app on the store. Apps that crash on launch are removed immediately, without the 90 days.

Two details matter for owners:

• The app keeps working for people who already have it. Apple says current users won't experience any interruption and can still make in-app purchases.
• There is no deadline to bring it back. Apple says a developer can resubmit at any time, as long as the membership is still active.

This is the reason that catches "finished" apps: the app works, nobody complained, so nobody updated it. Three years passes faster than it sounds.

The catch is that "submit an update" now means rebuilding with current tools. Since April 28, 2026, uploads must be built with Xcode 26 or later using the iOS 26 SDK, and since September 9, 2026, iOS apps must target iOS 13 or later (Apple: Upcoming requirements). A three-year-old project usually doesn't build cleanly with a new Xcode on the first try. Ninety days is enough if you start on day one.

Reason 2: the membership lapsed

The Apple Developer Program is a yearly membership. Apple's renewal page says that if the membership expires, your apps will no longer be available for download, and you can't submit new apps or updates. Apps already installed keep working.

Apple says renewal must be done by the Account Holder, who is also the person who can manage automatic renewal. So this reason has a very specific shape: the person who set up the account has left, changed email, or is a freelancer who stopped caring, and nobody else can renew.

If your app was published from a developer's account rather than your own, this is the risk you are carrying. We cover how to set that up correctly in how to give a developer access without giving up your app.

Reason 3: a requirement nobody read

Apple publishes a running list of dated requirements. Most of them block updates rather than remove apps, but at least one removes apps outright, and the others feed Reason 1 by making a required update harder.

From Apple's Upcoming requirements page:

• Trader status in the EU. Since February 17, 2025, apps without trader status are removed from the App Store in the European Union until trader status is provided and verified. If you sell in Europe and never answered the trader-status questions in App Store Connect, this is a real removal, region by region.
• Age rating updates. Developers were asked to respond to updated age rating questions by January 31, 2026, to avoid an interruption when submitting updates.
• Xcode and SDK minimums. Since April 28, 2026, uploads must use Xcode 26. This doesn't remove anything, but it means the "quick update" you planned to satisfy Reason 1 is not quick if your tooling is old.

We have had our own share of small, non-removal rejections along the way: App Store Connect refusing one app's release notes over a single emoji, and a build bounced at upload for a missing photo-library purpose string that a sharing library had pulled in (Apple's ITMS-90683). Neither removes an app. They cost cycles, which is exactly what you can't afford in the middle of a 90-day window. Our pre-release check now catches both before anything is uploaded.

Google Play does it differently

Google doesn't have a three-year rule, but two things play the same role:

• Apps that don't meet the yearly target API level stop being available to new users on newer Android versions. Existing users keep the app (Google Play target API level requirements).
• Google closes developer accounts it considers inactive: created more than a year ago and never submitted an app, or with fewer than 1,000 combined lifetime installs, unverified contact details, and no Play Console use in 180 days. The owner is emailed first, with reminders at 60, 30, and 7 days before closure, and the registration fee is not refunded (Closure of inactive developer accounts).

How to tell which one hit you

1. Sign in to App Store Connect and look at the app's status and any messages from App Review. Then look at the membership page: an expired membership is a different problem from a removed app.
2. Search the inbox tied to the Apple developer account for mail from Apple. The 90-day outdated-app notice arrives by email.
3. Check the membership page for the expiry date.

What to do this week

• Find out who the Account Holder is on your Apple account and confirm their email still works.
• Check the membership expiry date and whether automatic renewal is on.
• Note the date of your app's last update. If it is more than two years ago, plan an update now, before the three-year mark.
• If you sell in the EU, confirm trader status is set in App Store Connect.
• On Google Play, make sure the account's contact details are verified.

If you'd rather have someone read Apple's emails for you, that's part of App Care. It is the same desk that reads them for our own 17 apps, and the same yearly rebuild that keeps them from ever reaching the three-year mark.

Sources

• Apple, App Store Improvements: https://developer.apple.com/support/app-store-improvements/
• Apple, Membership renewal: https://developer.apple.com/support/renewal/
• Apple, Upcoming requirements: https://developer.apple.com/news/upcoming-requirements/
• Apple, App and submission statuses: https://developer.apple.com/help/app-store-connect/reference/app-and-submission-statuses
• Google Play target API level requirements: https://support.google.com/googleplay/android-developer/answer/11926878
• Google Play, Closure of inactive developer accounts: https://support.google.com/googleplay/android-developer/answer/11605267