Why is my review score dropping?

Usually because something turned players negative, and the most common fixable cause is bugs or crashes, often a recently introduced issue hitting many players. A review score reflects player satisfaction, so a drop means satisfaction fell, and the common technical causes are: a crash spike (an update introduced a crash many players hit), a bug that broke something players care about, lost progress (save corruption), or a performance regression. To find which, look at two things: recent negative reviews (what complaints recur, a crash, a bug, lag, lost progress) and your crash data around when the score started falling (did a crash spike or a release introduce an issue at that time?). If a specific issue shows up in both, the reviews complaining about it and your data showing it surged, that issue is likely driving the drop. So your review score is dropping most likely because a bug or crash (often recently introduced) is turning players negative, which you can confirm by matching recent negative review complaints against your crash data around the drop's timing. Bugnet captures crashes with per-version tracking, so you can check whether a crash spiked or a release introduced an issue when your score started dropping, and rank the issues by impact to see which are affecting the most players (and thus driving the most negative reviews), turning a mysterious score drop into a diagnosed cause you can fix, then show the fix via a changelog and let the score recover.

How do I recover a dropping review score?

Fix the high-impact issues driving the negativity, then show the fixes via a changelog and let positive reviews accumulate, recovery comes from resolving the underlying cause. A dropping review score driven by bugs is recoverable because the cause is fixable. First, identify what is driving it: match recent negative reviews against your crash data to find the high-impact issues (the crashes and bugs affecting the most players, generating the most negative reviews). Second, fix those at the root: rank by affected players and fix the worst first, since they drive the most reviews, fixing them has the biggest effect, stopping new players from hitting the issues and new negative reviews from the same cause. Third, show the fixes: use a changelog to demonstrate the issues are resolved (and which version fixed them), which reassures players and prompts some to revise reviews upward. As the high-impact issues stop driving negativity, the flow of new negative reviews slows and positive reviews accumulate, recovering the score. The key is fixing the highest-impact issues, since they generate the most negative reviews, fixing them moves the score most. So you recover a dropping review score by fixing the high-impact issues driving it (ranked by affected players), showing the fixes via a changelog (prompting revisions and reassuring players), and letting positive reviews accumulate as the cause is resolved. Bugnet supports this by capturing the issues behind the drop with impact ranking (so you fix the ones driving the most reviews first) and a changelog/tracker to show fixes (prompting revisions), so you can systematically reverse a bug-driven score drop by resolving its underlying causes.

Is my review score drop caused by a recent update?

Quite possibly, check whether the drop's timing aligns with a release and whether a crash spiked on that build, since updates that introduce crashes are a common cause of score drops. A review score that drops shortly after an update is a strong signal the update introduced a problem: a regression that crashed players, broke a feature, or hurt performance, turning them negative. To check, look at the timing: did your score start falling right after a release? Then check that build's stability per version: did the crash rate spike on the new build? Did new crashes appear? If the score drop aligns with a release that spiked the crash rate or introduced crashes, the update is likely the cause, a regression it introduced is hitting players and driving negative reviews. If the drop does not align with a release (the score fell without a recent update), the cause is something else, an external trigger like an OS update, or a non-technical cause. So your review score drop may well be caused by a recent update, check whether the drop's timing aligns with a release and whether that build spiked the crash rate or introduced new crashes (a per-version comparison), which would confirm an update-introduced regression as the cause. Bugnet tracks crash rate per version, so you can see whether a release coincided with your score drop and introduced crashes (the new build's crash rate climbing, new signatures appearing), confirming or ruling out a recent update as the cause, so you can roll back or hotfix the regression if the update is to blame, then show the fix and let the score recover.

What to Do When Your Review Score Drops

Quick answer: Check whether bugs or crashes are driving the drop via your crash data and recent reviews, fix the high-impact issues behind it, and show the fixes via a changelog to recover.

A falling review score is a warning that something is turning players negative, often a bug or crash. Finding and fixing the underlying cause is how you stop and reverse the decline. Here is what to do when your review score drops.

Check Whether Bugs or Crashes Are Driving It

A review score drop has a cause, and it is often technical: read recent negative reviews for recurring complaints (a crash, a bug, lost progress, performance) and check your crash data for issues that spiked around when the score started falling. If a crash or bug is showing up in both, it is likely driving the drop.

Bugnet captures crashes and tracks per version, so you can check whether a crash spiked or a release introduced an issue around when your score started dropping. Matching the timing of the drop against your crash data reveals whether bugs are driving it, the crashes that surged when the score fell are the likely cause.

Fix the High-Impact Issues Behind the Drop

Fix what is driving the negativity: rank your crashes and bugs by how many players each affects, and fix the high-impact ones at the root. These are the issues most players are hitting, so they generate the most negative reviews, and fixing them stops the flow of new ones.

Bugnet groups issues by signature and ranks by affected players with full context, so the high-impact issues behind the score drop are at the top of your list. Fixing them at the root stops the most players from hitting the problems driving negative reviews, which is what halts and reverses a score drop.

Show the Fixes and Let the Score Recover

Surface your fixes: use a changelog to show players the issues are fixed and which version resolved them, which reassures players and can prompt updated reviews. As the high-impact issues stop driving negativity, new positive reviews accumulate and the score recovers.

Bugnet gives you a public changelog and tracker, so you can show the issues behind the drop are fixed. Visible fixes reassure players and prompt some to revise reviews, and with the underlying issues resolved, the flow of bug-driven negative reviews stops, letting your score recover as positive reviews accumulate.

When your review score drops, check whether bugs or crashes are driving it (crash data and recent reviews), fix the high-impact issues at the root, and show the fixes via a changelog. Bug-driven drops are recoverable.