Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Google Play says my app crashes too much or freezes too often

Short answer

Google Play sets bad behavior thresholds: a user-perceived crash rate of at least 1.09% of daily users overall, or 8% on a single device model, and similar ANR limits of 0.47% and 8%. It generally uses the last 28 days. Above them, the app is likely less discoverable.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Play Console shows a warning on my app's page.
  • Android vitals is red for crashes or 'app not responding'.
  • Downloads dropped and I do not know why.
  • My developer says it only happens on one phone brand.
  • I cannot read the crash reports in the Console.

Why does this happen?

  1. The overall crash or freeze rate is too high

    Google lists at least 1.09% of daily users with a user-perceived crash, or at least 0.47% with a user-perceived ANR, across all device models.

  2. One device model is much worse

    The per-device thresholds are at least 8% of daily users for crashes or for ANRs on a single model. One phone type can trigger it while the rest are fine.

  3. The measurement window is long

    Google says it generally considers the last 28 days but may act sooner after a spike, so a fix takes time to show.

  4. The cause is in the code or a new release

    A new update, a changed library or a heavy screen can add crashes or freezes.

What can I do about it today?

  1. Open Android vitals and read itIn Play Console look at crash and ANR rates, and which versions and devices are worst. Ask whoever holds the account to share a screenshot.
  2. Note when it beganIf it began with a release, say which one. Do not roll back or unpublish before checking with your developer.
  3. Do not ignore itGoogle says apps over a threshold are likely to be less discoverable, and that for per-device issues it may steer users on those devices to other titles.
  4. Collect the top crash reasonsAsk for the three most frequent stack traces, not a full list.
  5. Pause risky releasesDo not push new features until the main crash is understood.

When should I bring someone in?

  • The crash or freeze rate stays above a threshold after a fix.
  • The app has no crash reporting beyond the Console.
  • The warning shows on your store listing.

How do I handle it?

  1. Rank crashes by users affectedI sort the Console's clusters by how many users they hit, not how often a developer saw them.
  2. Reproduce on the worst deviceI test on that device model or a close one, or in an emulator with similar memory.
  3. Fix, then roll out in stagesI release to a small percentage first and watch the rate.
  4. Add reporting that outlasts the ConsoleI make sure crashes are also reported to a tool you control.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

How fast does the warning go away?

It depends on the 28-day window Google uses, so improvement shows gradually.

Is this a ban?

Google's page describes reduced discoverability and in some cases a warning on the listing, not a removal.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.