Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Google's pre-launch report says my Android app crashed or failed

Short answer

Google's pre-launch report installs your app on real test devices, crawls it for a few minutes and lists stability, performance, accessibility and compatibility issues. A crash can come from your app or from a missing login. Open the report, read the stack trace, and check whether the test account was provided.

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

Does this sound like your situation?

  • Play Console shows a pre-launch report with crashes or errors.
  • The report says Test failed or never finishes.
  • The crash happens on devices I do not own.
  • The app works for me but the report says it crashes on start.
  • I am not sure whether the warnings block my release.

Why does this happen?

  1. The app really crashes on some devices

    Google says the report installs your app on test lab devices, launches it and crawls it for several minutes with taps, typing and swipes. The devices are chosen to cover many makers and Android versions, so problems that never appear on your own phone can show up.

  2. The app needs a login the report does not have

    Google says you can add login credentials in the report settings, using a dedicated test account. Credentials work only with standard Android widgets, not custom controls or web-based sign-in.

  3. The test could not run

    Google says Test failed means it could not run, and apps without a main launch activity cannot be tested. If a report is not finished after two days, Google advises uploading the file again.

  4. Features the test cannot do

    Google lists limits: apps that check for root access are not supported, test devices cannot make purchases and cannot be preloaded with media or extra apps. An app that needs those can fail for reasons that real users never meet.

  5. The warnings are about quality, not only crashes

    Google says the report covers stability, Android compatibility, performance and accessibility, and shows counts of errors, warnings and minor issues with a launch recommendation.

What can I do about it today?

  1. Open the Overview pageIt shows counts of errors, warnings and minor issues and a launch recommendation. Take a screenshot.
  2. Open the detailsUse Show summary, then View details, to see the stack traces and screenshots for each problem.
  3. Send the report to your developerForward the screenshots and ask which problems are real crashes and which come from the test itself.
  4. Check whether a test account was addedIf the app needs a login, ask for a dedicated test account to be added in the report settings.
  5. Do not release in a hurryA crash on test devices can show a problem for real customers too. Wait for a clear answer.

When should I bring someone in?

  • The report shows crashes on start that your developer cannot reproduce.
  • The app has a complex sign-in that the test cannot pass.
  • You are about to release and the report is red.

How do I handle it?

  1. Sort the findingsI separate real crashes from test limitations such as login, purchases or missing media.
  2. Reproduce the crashI run the app on a similar device or emulator and read the stack trace.
  3. Fix and re-uploadThe fix goes into a new build, and I check the new report before release.
  4. Set up the test accountWhere a login is needed, I add a dedicated test account in the report settings.

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?

Does the report block my release?

The Google page I read does not say it blocks releases. It gives a launch recommendation, so treat red results seriously.

How long does it take?

Google says results usually arrive in under an hour, though sometimes hours later.

Where are the test devices?

Google says the test devices are located in the United States and that you cannot customise the device set in Play Console.

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.