How to handle a wave of 1-star reviews after a bad update

It can happen to any app maker. You ship an update, and the next morning your reviews are on fire. One-star after one-star. The rating you worked hard for starts to slide.

Take a breath. A bad week does not have to become a bad year. This guide gives you a calm plan for the first days, and a checklist to make the next release safer.

What should you do first when bad reviews pour in?

Find out what broke before you do anything else. Don't reply yet, don't argue, and don't post a vague apology. Spend the first hour reading.

1. Read the newest 1- and 2-star reviews. Look at the version number and the date on each one.
2. Group them by problem. Crash on launch? Lost data? A missing feature? A new price?
3. Count each group. Often one or two problems stand out.
4. Check your crash reports and support inbox for the same issues.

How do you find out what broke?

Match what users say with what changed. Make a short list of everything in the release: code changes, design changes, price changes and removed features. Then line up each review theme with an item on that list.

Look for three common causes:

• A bug. Crashes, freezes, broken sync or a failed login. These are urgent.
• A change people didn't want. A redesign, a moved button or a removed feature.
• A price or paywall change. A feature that used to be free now isn't.

Each one needs a different fix. A bug needs code. An unwanted change may need a setting, a rollback or a clearer explanation. A price change needs honest words and maybe a better offer for loyal users.

How do you stop the damage?

Limit how many people get the bad version, then ship a fix fast.

Pause your phased release. If you released the update in phases, you can pause it in App Store Connect. Apple's phased release sends an update to people with automatic updates over 7 days. You can pause it for up to 30 days in total. Keep in mind that anyone can still download the update by hand from the App Store.

Turn off the broken part. If the bad feature sits behind a remote switch on your server, turn it off now. This is one reason to ship big changes behind a switch you control.

Ship a fix. Keep the fix small and focused. Don't bundle new features with it.

Ask for an expedited review. If the bug is critical, submit the fix, then fill in Apple's Request an Expedited App Review form. Explain the critical bug in the Notes field when you submit. Apple says it will expedite reviews as availability and demand allow, so it's not guaranteed.

Tell users in the app. If people can still open the app, a short in-app message helps: "We know sync broke in 4.2. A fix is on the way."

How should you reply during a wave of bad reviews?

Reply in two rounds: once to say you know, and once to say it's fixed. Keep both short and honest.

Round one, while you work on the fix: reply to the most detailed and most visible reviews. You don't need to answer all of them yet.

Round two, once the fix is live: go back and reply to every review about the issue. Apple tells reviewers when you reply, and they can update their review. This is your best chance to win back stars.

For more templates, see our guide on how to respond to App Store reviews.

Should you reset your rating after the fix?

Maybe. When you release a new version, you can choose to reset your overall rating. It starts fresh in every country at once. Written reviews stay on your page.

A reset makes sense when the fix is solid and the bad rating no longer reflects your app. Think twice if you don't have many active users to rate the new version. Your page will show a "recently reset" note until enough people rate again. And once the new version is out, you can't bring the old rating back.

Read App Store ratings explained for the full details.

What if it's review bombing, not a bug?

Sometimes the reviews aren't about a bug at all. They might be about a price change, a policy, or news about your company. A sudden wave like that is called review bombing.

You can't delete these reviews. Here's what you can do:

• Stay calm and stay polite. Angry replies make it worse.
• Explain once, clearly. If you changed the price, say why in plain words. Put the same note in your release notes.
• Listen for a real point. Even an unfair wave can hide a fair complaint.
• Focus on the people who stay. Keep shipping, and keep asking happy users for ratings at good moments. Over time, new reviews will outnumber the wave.

How do you prevent the next bad update?

Bad releases often share the same causes. A short checklist can catch a lot of them:

• Test the release on old and new devices, and on the oldest iOS version you support.
• Run a TestFlight beta with real users before every big release.
• Use phased release, so a bad update reaches fewer people at first.
• Put risky features behind a switch you can turn off from your server.
• Write release notes in plain words, and warn users about big changes.
• Never remove a popular feature without a heads-up and a reason.
• Watch your reviews every day for a week after each release.

That last one matters most. The sooner you spot a problem, the fewer people it hurts. Our guide on getting more App Store reviews shows how to keep good ratings coming once things are calm again.