How to Use the Google Play Pre-launch Report in a Closed Test
Google Play generates a pre-launch report automatically when you upload an app bundle, subject to device lab capacity. It installs your app on test devices, crawls it for several minutes and reports stability, performance and accessibility issues, including crashes and ANRs. Run it on every closed test build and fix errors before you apply for production.
While your closed testers use your app, Google Play runs its own automated test on every build you upload. That test produces the pre-launch report: a list of crashes, ANRs, performance problems and accessibility issues found on Google's test devices. This guide explains how it works and how to use it during your closed test, using only what Google documents in its Help Center.
The facts here come from Google's articles Use a pre-launch report to identify issues, Understand your pre-launch report and View crashes and application not responding errors, plus the testing requirements page linked below.
What does the pre-launch report test?
Google says pre-launch reports are generated automatically when you upload an app bundle or APK, subject to capacity within its device lab. Each artifact is tested when it is uploaded and when it is saved to production, so issues can be found before your app reaches users. The report includes tests for:
- Stability issues, such as crashes and ANRs
- Android compatibility issues, such as use of interfaces that aren't in the public Android SDK
- Performance issues
- Accessibility issues
Not every app can be tested. Google notes that test devices can't run tests on apps without a main launch activity, which includes launchers, widgets, keyboards and watch faces. The test platform also doesn't support apps that check whether a device is rooted.
When does it run during a closed test?
Because the report runs on upload, each new build you prepare for your closed test gets its own report. Google says you'll usually receive results within an hour of uploading your app bundle, and in some cases several hours after upload. If the report is not complete after two days, Google suggests uploading your artifact again, which triggers a new report.
On the report pages you may see two status messages. Testing in progress means your latest test hasn't finished yet. Test failed means your latest test couldn't run. In both cases Google's advice for running another test is to publish another app bundle.
A licensing detail matters for closed tests. According to Google, if your app uses a Google Play licensing service and is not in an open test and has no active app bundle in production, it will fail the licensing check during testing. You still get results, but your app runs in an unlicensed state. Google's suggestion is to publish a closed version of your app with licensing services disabled.
How does the crawler test your app?
Google describes the process in Use a pre-launch report to identify issues. Your app is installed on a set of Android devices in Google's test lab, then launched and crawled automatically for several minutes. The crawler performs basic actions such as typing, tapping and swiping. When the crawl is finished, the results are compiled into the report and your app is uninstalled from all test lab devices.
A few facts about the test devices help you judge what the report can and can't see:
- Device choice. Google chooses devices for breadth of coverage, taking into account device popularity, crash frequency, screen resolutions, manufacturers and Android OS version. The selection may vary. Devices you excluded in your app manifest are excluded from tests too.
- Android versions and form factors. The device set includes devices on Android 9 and above, covering phones, tablets, Wear OS and desktop devices like Chromebooks. Android Automotive OS and Android TV can't be tested directly.
- Location. Test devices are located in the United States, so an app with country-based content only shows what's available there.
- Purchases and ads. Test devices can't make purchases, so parts of your app behind subscriptions or in-app products may not be tested. Google ads already exclude pre-launch report traffic; for other ad networks you need to exclude Google's IP address ranges yourself.
- Orientation. Tests run in portrait by default. If your app is locked to landscape, you should see landscape screenshots and videos.
How do you get the crawler past sign-in?
If your app opens on a sign-in screen, the crawler can't test what's behind it unless you help. Google offers these settings on the Pre-launch report settings page (Test and release > Testing > Pre-launch report > Settings):
- Test account credentials. Select Provide credentials and enter a username and password. You don't need them if your app supports Sign-in with Google, which lets the crawler log in automatically, or if you've already provided credentials on the App content page. Google recommends creating a test account rather than using official credentials. Credentials only work in apps that use standard Android widgets, not in apps that render custom controls with OpenGL or use a WebView for sign-in.
- A Robo script. To control the steps the crawler takes, for example a common user journey, you can record a Robo script with the Firebase tool in Android Studio and upload it. The crawler runs your scripted actions first, then explores as usual. Google notes you don't need a Firebase account.
- A game loop. For a game or an app that uses OpenGL, Google says you need a game loop to get a good report. The crawler detects and runs it automatically.
- Deep links. You can add up to three deep links. After the main crawl, the crawler visits each one in turn and crawls for a further 30 seconds.
- Languages. You can select up to five languages to see results for. Because the first test runs on upload, you can only add language preferences after the initial test is completed.
How do you read the results?
Open Test and release > Testing > Pre-launch report > Overview. Google's Understand your pre-launch report article says the overview summarises the errors, warnings and minor issues found, grouped by issue type, with the number of devices tested and a recommendation based on the results. Google gives these examples:
- Errors: crashes, ANRs, use of defective libraries, and use of unsupported APIs that have been restricted.
- Warnings: slow startup and load times, sign-in or crawl issues, memory issues, and use of unsupported APIs that aren't yet restricted.
- Minor issues: missing content labels, color contrast issues, small touch target sizes and implementation issues.
The Details page has Stability, Performance, Accessibility and Screenshots tabs, with stack traces, screenshots and charts. On the Stability tab, each issue shows how many devices it was detected on and its stack trace, and you can open a device to see its specifications, a screenshot and video from testing. For non-SDK interfaces, Google suggests fixing them in this order: restricted, then unsupported with restriction imminent, then unsupported with restriction not imminent. The Performance tab reports average CPU, memory and network use per device model, and you can compare a spike with the action the crawler took at that moment.
If your code is obfuscated or stripped, the report still runs, but crash and ANR stack traces will be obfuscated too. Google recommends uploading a deobfuscation or symbolication file so they are easier to debug. Previous reports are listed in the "Report details" table at the bottom of the Overview page.
Do pre-launch crashes count in Android vitals?
No. Google says crashes found while generating a pre-launch report come from test devices, so they don't affect your crash statistics. Android vitals is separate: in View crashes and application not responding errors, Google explains that crash and ANR data in Monitor and improve > Android vitals > Crashes and ANRs comes from Android devices whose users have opted in to automatically share usage and diagnostics data.
The two views do connect. When you select a crash or ANR cluster in Android vitals, Google shows a separate section if the same issue was also found while generating a pre-launch report, with device information, crash or ANR details, the device's Logcat and a video of the error. Google also notes that user-perceived crash rate and user-perceived ANR rate are core vitals that affect your app's discoverability on Google Play, which is a good reason to fix pre-launch errors before real users meet them.
How does it fit into your closed test?
Google's App testing requirements for new personal developer accounts page recommends setting up and running a pre-launch report to find issues before they reach users, through a report listing warnings, errors and performance issues. It doesn't replace your testers. Google notes that the tests may not identify all issues, and the crawler only explores for minutes, while your closed test needs testers opted in for 14 days. Our guide to the 12 testers for 14 days rule explains that count.
A practical routine: check the report after each build you send to your testers, fix errors first, then compare what the report found with what testers told you. When you apply, Google asks what you changed after testing; our guide to applying for production access covers the form, and the production access checklist lists the points to confirm before you apply.
Frequently asked questions
Does the pre-launch report run automatically?
Yes. Google says pre-launch reports are generated automatically when you upload an app bundle or APK, or when you save a production release, where capacity in Google's device lab permits.
How long does a pre-launch report take?
Google says you'll usually receive results within an hour of uploading your app bundle, and in some cases several hours after upload. If the report is not complete after two days, Google suggests uploading your artifact again to trigger a new report.
Do crashes in the pre-launch report affect my crash rate?
No. Google says crashes found while generating a pre-launch report come from test devices, so they don't affect your crash statistics.
Can the pre-launch report test screens behind a sign-in?
Yes, if you provide test account credentials in the pre-launch report settings, or if your app supports Sign-in with Google. Credentials only work in apps that use standard Android widgets, not OpenGL custom controls or a WebView sign-in flow.
Does a clean pre-launch report mean my app is ready for production?
Not on its own. Google notes that the tests may not identify all issues. Personal accounts created after 13 November 2023 also need a closed test with at least 12 testers opted in for the last 14 days before they can apply for production access.