Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My app crashes for some customers and works for me

Short answer

A crash that affects only some users depends on something that differs: phone model, Android or iOS version, memory, network, app version or what they did. Play Console and App Store Connect group crash data by those details. Collect the phone and version from affected users and let a developer read the crash reports.

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

Does this sound like your situation?

  • The app works perfectly on my phone but customers say it closes by itself.
  • Reviews mention crashes on a specific phone brand or a version of Android.
  • I cannot reproduce the problem however I try.
  • It crashes on a particular screen, such as the photo upload or checkout.
  • Crashes began with the last update, or only for people who did not update.

Why does this happen?

  1. Phones differ more than owners expect

    Google says a crash can be tied to the Android version, device type or app version, and recommends looking for a correlation between them. Development setups usually have more memory, bandwidth and storage than customers' phones.

  2. A crash is an unhandled error

    Google defines a crash as an unexpected exit caused by an unhandled exception or signal. Network exceptions in particular are normal operating conditions, since users move in and out of coverage, and the app is expected to handle them.

  3. Missing values are the biggest cause

    Google states that null pointer exceptions are the largest cause of app crashes on Google Play. They happen when the app uses information that is not there, which can depend on what a particular customer entered or has stored.

  4. The crash data shows the pattern

    Android vitals reports the share of daily users who had a crash, and breaks it down by app version, Android version, form factor, device model and country.

  5. Crash rates affect visibility

    Google lists a bad behaviour threshold for the user-perceived crash rate, and says exceeding it makes an app likely less discoverable on Google Play.

What can I do about it today?

  1. Ask affected customers the same questionsPhone make and model, operating system version, app version, what they tapped just before and whether it happens every time.
  2. Look for the common threadPut the answers in a table. If every case is one phone brand, one OS version or one feature, you have found where to look.
  3. Open crash numbers in the store consolesPlay Console's Android vitals and App Store Connect crash reports show how many users are affected. Take screenshots for your developer.
  4. Check which app version they runIf most crashes are in an old version, an update may already contain the fix. Encourage updating.
  5. Try the app with weak internet and low storageCustomers rarely have your fast connection and spare space. Test on an older phone if you have one.
  6. Do not delete your reviews or reply defensivelyReply that you are investigating and ask for the phone and version. It helps both the fix and the rating.

When should I bring someone in?

  • The numbers in the store console are rising.
  • Crashes happen on a payment, booking or sign-in step.
  • Nobody on your side can read a crash report.

How do I handle it?

  1. Read the crash reportsI group reports by the stack trace, then by version and device, so the biggest fault comes first.
  2. Reproduce on matching conditionsI use a device or emulator with the same OS version and limits, such as low memory or a poor network.
  3. Fix the cause and add protectionThe failing step is repaired, and the app is made to handle missing data and network errors without closing.
  4. Put crash reporting in placeIf the app has no reporting tool, I add one, so future crashes arrive with details instead of complaints.
  5. Release and watch the numbersAfter release I compare crash figures per version to confirm the fault is gone.

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?

Why can I never reproduce it?

Your phone, account and network differ from the customer's. The crash report shows what the customer's device was doing.

Is it the customer's phone?

Rarely. Even when it only affects one model, the app is expected to run on the phones it is offered to.

How many crashes is too many?

Google's page gives a user-perceived crash rate threshold for Android vitals and says exceeding it makes an app likely less discoverable. Check your own figures in the Console.

Can you find it from a review alone?

Sometimes the review names the phone and screen, which is a start. A crash report is the faster way.

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.