How to respond to 1-star reviews after a bad app update

Español · Deutsch · Polski · Français

A broken release produces a wave of 1-star reviews within hours. Here is how to handle it without breaking store rules.

Free app review check · Review export · Reply generator · Sample report · Report €19 · Competitor Pack €29 · Monitor €29/month

1. Confirm it is the update

2. Reply to the worst reviews first

Apple recommends prioritising the lowest-rated reviews and those about technical issues (Apple Developer: Ratings, reviews, and responses). Keep replies specific: name the bug, say you are working on it, give one support channel. Don't promise a date you can't keep, and don't ask for a better rating; Google's policy says replies must not ask for a higher rating (Play Console Help: Ratings, Reviews, and Installs policy).

"Thanks for reporting this. Version 6.3 breaks login for some accounts that use Sign in with Apple. We're fixing it now. Until the update is out, the web version works: yourapp.com. – The Yourapp team"

3. Ship the fix and say so

Tell users in the release notes what you fixed (Apple Developer: Creating your product page). Then reply again to the reviews that reported the problem (Apple Developer: Ratings, reviews, and responses).

4. Know who gets notified

5. Recover the rating

More reply patterns by complaint type: How to reply to 1-star App Store reviews.

Sources

Related guides

Questions

Should I reply to every 1-star review after a bad update?

Reply to the lowest-rated and most specific ones first, as Apple recommends, then reply again to the same reviews once the fix ships.

Will users see my reply if I edit it after the fix?

On the App Store the latest response is shown. On Google Play, the user isn't notified when you edit a reply, only after your first reply to a new or updated review.

Can I remove the bad ratings from the broken version?

On the App Store you can reset the overview rating with a new version; written reviews stay. Google Play has no reset.