Lorixen.
EN

A Bad App Release Is Live: What You Can Undo on the App Store and Google Play

Short answer: You cannot pull a bad update off people's phones, and neither store lets you simply swap the live app back to an older file. What you can do is stop the spread by pausing a phased release or halting a staged rollout, switch off the broken feature from your server if you built a switch, and submit a corrected build with a higher number as quickly as possible. The time you save depends on what you set up before the incident, which is why the last section matters as much as the first.

Stage 1: The first hour

Resist the urge to upload anything yet. First establish facts.

  1. Confirm the problem. What breaks, for whom, on which devices and versions? A crash on sign-in for Android 13 phones is a different job from a wrong total on one screen.
  2. Count the spread. Check crash reports, support messages and reviews. Note how many people have the new version. If the release was staged, the number may still be small.
  3. Decide the severity. Data loss, failed payments and people locked out are urgent. A mis-aligned button is not.
  4. Stop the bleeding. See the next section.
  5. Tell the team and key customers in plain words, before they find out themselves.

Stage 2: What each store lets you do

Apple App Store

If you used a phased release, App Store Connect lets you pause it. Apple's documentation describes a seven-day automatic rollout to people with automatic updates turned on, and you can pause for a limited time and resume. People who already received the version keep it, and anybody who downloads manually from the store can still get the latest version. Check the current rules on the official page, as the details are Apple's to change.

You cannot restore a previous binary as the live version. The route back is a new build, with a higher build number, submitted for review. If the issue is serious, Apple offers a way to ask for expedited review, which is worth a short, factual request.

You can also remove the app from sale. That is a heavy step, hiding the app from new downloads while existing users keep it, and it is only for severe cases.

Google Play

If you released through a staged rollout, you can halt it in Play Console, which stops further users receiving that version. People who already updated keep it. Google's help page on staged rollouts explains the controls.

As with Apple, you cannot make users go back. You can publish a fixed build with a higher version code. A common emergency move is to rebuild the previous good code under a new version code and release it, because that can be quicker than debugging under pressure. Google Play reviews updates, usually faster for established apps, though timing is not guaranteed.

Your own server

Often the strongest lever is not in the store at all. If the broken behaviour depends on server data or an API response, you may be able to fix it there in minutes. A feature flag, which is a setting on your server that turns a feature on or off without a new app version, is the best tool, as it lets the app skip the broken feature at once.

Stage 3: Shipping the fix

  • Fix only the cause. This is not the time for extra features.
  • Test the fix against the exact case that failed, plus the five tasks your customers do most.
  • Raise the build and version numbers properly.
  • Write review notes saying it is a fix for a live issue, and keep them factual.
  • Submit on both platforms if both are affected, and prepare a manual release so you control timing.
  • If the broken version has a force-update mechanism, use it for the fixed version only when you are sure, since a blocking update that is itself faulty makes things worse.

Illustrative example: a fictional florist's app ships version 3.2.0 on a Tuesday. By lunchtime, orders placed with a discount code show a negative total. The team halts the staged rollout at 15 percent, turns off the discount feature through a server flag, and submits 3.2.1 with the pricing fix the same afternoon. People on 3.2.0 still have the old build but the flagged feature is off, and orders carry on.

Stage 4: Cleaning up afterwards

Fixing the build is half the job. Then:

  • Contact affected customers if money or data was involved
  • Correct bad orders, records or charges, using a list pulled from your database
  • Reply to negative reviews with a calm explanation and the fixed version number
  • Write a short review of what happened: cause, how it was found, how long it lasted, what changes

Do not hunt for someone to blame. Look for the missing safety net.

Preparing before the next incident

Safety net What it gives you
Staged or phased rollout Only a share of users see a bad build first
Feature flags on the server Switch off a feature without a store review
Crash reporting You hear about problems before the reviews arrive
Release log You know exactly which build is live and what it contains
A previous known-good build kept ready A fast base for an emergency rebuild
A named person with store access and authority No waiting while the one login holder is on a plane
A short incident checklist Calm steps instead of improvisation

Not every small business needs every item. A staged rollout, crash reporting and one feature flag for risky features already change the picture.

Mistakes during an incident

Submitting three fixes in a day. Each submission restarts review. One careful fix beats three rushed ones.

Fixing without reproducing. If you cannot make the fault happen, you cannot be sure you fixed it.

Silence. Customers forgive a clear note far faster than a mystery.

Skipping the server side. The app may not be the real culprit.

FAQ

Can we ask Apple or Google to reverse the update for everyone?

No, not as a routine option. Plan around pausing, patching and server switches.

Will users lose data if they update again?

A well-built app migrates data between versions. If your bad release changed the local data format, test the fix on a phone that already has the bad version before shipping.

Should we force everyone to update?

Only after the fix is live and tested, and only if the old version is dangerous.

How long does review take in an emergency?

Neither store guarantees a time. Apple's expedited route is a request, not a promise.

If you want a safety net in place before your next release, talk to us about staged rollouts, feature flags and a release routine for your app.

Sources

WhatsAppBook a call