Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

The new version of my app keeps crashing

Short answer

If an update crashes, first stop it reaching more people: halt the staged rollout on Google Play or pause the phased release on the App Store. Users who already updated stay on the bad version until a fixed one is released, so the real cure is a corrected build. Find the crash in the store's reports.

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

Does this sound like your situation?

  • Customers say the app closes by itself right after the latest update.
  • Reviews mention crashes since the new version.
  • It crashes for some phones and not others.
  • It crashes at start, so nobody can even log in.
  • The previous version was stable.

Why does this happen?

  1. An unhandled error ends the app

    Google defines a crash as an unexpected exit caused by an unhandled exception or signal. Android shows a dialog saying the app has stopped, and the crash leaves a stack trace that can be read in Android vitals or in the device log.

  2. Null values are the largest known cause

    Google's guide says null pointer exceptions are the largest cause of app crashes on Google Play. A new field or screen that was not checked for missing data is a typical example.

  3. A plugin or setup change broke on some devices

    A new library, a version change or a missing initialisation can crash only on certain phones or at start.

  4. A value was used before it was ready

    Code that reads data before it has loaded can fail at startup.

  5. The update reached everyone at once

    A staged rollout sends an update to a percentage of users and the percentage does not rise by itself. Without one, a bad build reaches every user quickly.

What can I do about it today?

  1. Stop the spreadOn Google Play, halt the staged rollout. Google says halting stops the update reaching more users but does not roll back users who already have it. On the App Store, pause a phased release if you are using one.
  2. Do not delete the app or the listingThat loses reviews and users. A fix is a new version.
  3. Collect facts from a few usersPhone model, system version, app version, and what they were doing when it closed.
  4. Open the store's crash reportsPlay Console's Android vitals shows stack traces. Save screenshots; do not edit anything.
  5. Tell customers brieflySay you know and a fix is on its way, without a date you cannot control.

When should I bring someone in?

  • It crashes at start for a large share of users.
  • Your developer cannot reproduce it.
  • Orders, bookings or logins are blocked.

How do I handle it?

  1. Reproduce itUsing the reports and the affected phone and system versions, I recreate the crash.
  2. Fix the cause, not the symptomA narrow change that addresses the stack trace, with a test for that case.
  3. Release carefullyA staged rollout with the percentage raised only after the crash reports stay clean. Store review timing is not in my control.
  4. Keep a tested rollback readyFor any server-side part of the change, I keep a way back.

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?

Can I roll everyone back to the old version?

Per Google's help page, halting a rollout does not roll users back, and the suggested way forward is a new version with a fixed bundle.

Can the App Store rollout be paused?

Apple's phased release can be paused for up to 30 days in total, and it resumes where it was left off.

Will ratings recover?

A stable release lets new ratings come in. I cannot promise a number.

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.