Use a pre-launch report to identify issues

To generate your app's pre-launch report, publish your app on a closed or open test track.

You will automatically receive a pre-launch report for any app that you publish on a test track unless you opt-out. You'll usually receive test results within an hour of uploading your app bundle. In some cases, you'll receive results several hours after upload.

You can receive email notifications for available pre-launch reports by following these steps:

1. Open Play Console > Notifications.
2. Scroll down to "Pre-launch report" and tick the box next to it. You can choose to receive emails for all tests or only tests with issues.

Pre-launch reports are automatically generated when you publish an app on a closed or open test track. To disable all pre-launch reports for your app:

1. Open Play Console> Pre-launch report > Settings.
2. Scroll down to "Preferences," and untick the "Turn on pre-launch report" box to disable the report for your app.
3. Click Save.

1. Open Play Console.
2. Select an app.
3. On the left menu, select Testing > Pre-launch report > Settings.
4. Make your changes:
   • To edit credentials: In the “Test account credentials” section, enter your updated credentials in the username and password fields.
   • To remove credentials: In the “Test account credentials” section, select Don’t provide credentials.
     • Note: If you remove your app's test credentials, you'll need to add new credentials before any future tests can sign in to your app.
5. Click Save. These credentials will be used for all future tests unless edited.

If you’re testing a game or an app that uses OpenGL, you need to provide a game loop to get a good pre-launch report. A game loop defines the actions that you want the crawler to take. You can test more than one game loop in the same app.

To use game loops in your pre-launch report:

1. Modify your game to do the following:
   • Launch the loop
   • Run the loop
   • Close the loop (optional). You make these modifications in your development environment. For details, go to the Firebase Help Center.
     • Note: You don't need a Firebase account to use game loops in the pre-launch report.
2. Publish the version of your game with the game loop to a closed or open test track. The crawler will automatically detect and execute the game loop.

1. Open Play Console.
2. Select an app.
3. On the left menu, select Testing > Pre-launch report > Settings.
4. Under "Test your app in specific languages," select + Add language.
5. Select up to five languages. For future tests, you'll only see test results from these languages.
   • Note: If you don’t select any languages, we’ll automatically select languages in which your app has the most installs.
6. Click Save.

To view a summary of your pre-launch report:

1. Open Play Console.
2. Select an app.
3. Select Testing > Pre-launch report > Overview.
4. Review each section:
   • Stability
   • Performance
   • Accessibility
   • Security and trust
5. If any section has an issue, select Show summary to expand.
6. Select View details to see more granular information for your issues.
7. To view previous pre-launch reports, scroll to the table in the “Report details” section at the bottom of the page.

Note: If you see "Testing in progress," your latest test hasn't finished yet. If your latest test couldn't run, you may see "Test failed." To run another test, publish another app bundle.

To view detailed results of your pre-launch report:

1. Open Play Console.
2. Select an app.
3. Select Testing > Pre-launch report > Details.
4. Review the Stability, Performance, Accessibility, Screenshots, and Security and trust tabs. On each page, you'll see full details of the results of your latest test, including stack traces, screenshots, and charts.

Note: If you see "Testing in progress," your latest test hasn't finished yet. If your latest test couldn't run, you may see "Test failed." To run another test, publish another app bundle.

You'll usually receive test results within an hour of uploading your app bundle. In some cases, you'll receive results several hours after upload. If the report is not complete after two days, try uploading your artifact again. This will trigger a new report.

You can still get a pre-launch report if you are happy to make minor modifications to your code.

Test devices are located in the United States. If your app uses geolocation or has content restrictions based on country, test devices can only show what's available in their location.

If you need to test your app on a geolocation outside of where test devices are located, you can publish an app bundle that removes location requirements for testing purposes. There are two ways you can detect that your pre-launch reports are running in Test Lab:

• You can allowlist the IP address blocks documented in this Firebase Test Lab Overview.
• You can check Modify instrumented test behavior for Test Lab by adding a system variable.

The test platform doesn't support apps that check whether a device has privileged control (root access) on Android.

Google ads already exclude traffic from the pre-launch report address ranges. For other ad networks, you need to specify the IP address ranges to be excluded.

For details on how to mitigate fraudulent ad revenue with automated app testing, review the Google Developers site.

Test devices aren't able to make purchases during testing. If your app offers subscriptions or in-app products to access some parts of your app, testing scenarios may be limited.

Yes. Pre-launch report tests will run regardless.

If your code is obfuscated or stripped, however, any crashes or ANRs found during testing will have stack traces that are also obfuscated or stripped. To enable us to make your stack traces easier to debug, we recommend that you upload a deobfuscation or symbolication file.

You can learn more about uploading deobfuscation or symbolication files.

No. The test platform doesn't support pre-loading devices with media or pre-installed apps.

However, if you want to run tests on an app with pre-loaded data, you can publish a test version of your app with your media files embedded in its app bundle.

If your app is in an open test or your app has been published to production, pre-launch report testing will use an ID that acts as if it's licensed for your app.

If your app is not in an open test and doesn't have an active app bundle published to production, your app will fail the licensing check. You'll still receive pre-launch report results, but your app will be in an unlicensed state. To run tests on these apps, you can publish a closed version of your app with licensing services disabled.

The test devices are predefined to run tests on fixed portrait page orientation by default. However, if your app is locked to landscape, you should see videos and screenshots in landscape mode.

We choose test devices that provide a good breadth of coverage across the ecosystem, and take into account device popularity, crash frequency, screen resolutions, manufacturers, Android OS version, and more. The selection of test devices may vary.

If you have excluded some devices from targeting in your app manifest, then the pre-launch report will also exclude them in tests, but will not target any extra devices for your app.

The pre-launch report is powered by Firebase Test Lab. To customize the devices that are tested, consider conducting your own tests in the Firebase console.

Yes, we will run the app on an emulator and crawl it as we would with a physical device.

Our device set covers phones, tablets, Wear OS, and Desktop devices like Chromebooks. It is not possible to test apps directly on Android Auto or Android TV devices.

Our device set includes devices Android 9 and above.