How to Read the Google Play Pre-Launch Report
Play Console’s pre-launch report tests your build on real devices automatically. How it’s triggered, what each section means, and what to fix.
Short answer
The pre-launch report runs automatically when you upload an app bundle or APK (subject to device lab capacity). Google installs your app on a range of real devices running Android 9 and above, crawls it, and reports crashes, ANRs, performance, accessibility and security warnings with screenshots. It’s free QA before your testers ever open the app.
Where to find it
Play Console → your app → Test and release → Pre-launch report (labels vary). Each uploaded version gets its own report after a short wait.
What it tests
Google says the device set includes phones, tablets, Wear OS and desktop devices like Chromebooks, on Android 9 and above, and that the selection may vary. A robot crawler taps through your app for a few minutes on each device.
Sections and what to do
| Section | What it shows | Act when |
|---|---|---|
| Stability | Crashes and ANRs, with stack traces | Any crash. Fix before testers arrive |
| Performance | Startup time, frame rendering | Slow startup on low-end devices |
| Accessibility | Small touch targets, low contrast, missing labels | Always worth fixing. Helps everyone |
| Screenshots | What the robot saw on each device | Layout broken on a screen size |
| Security and trust | Known vulnerable libraries, unsafe patterns | Any warning with a fix available |
Getting past a login screen
If your app needs sign-in, the crawler stalls on the login screen. Provide test credentials in the pre-launch report settings so it can explore further. Never use a real user’s account.
Limits
- A robot isn’t a person. It won’t judge confusing flows or whether a feature is useful.
- It won’t replace the 12 human testers Google requires.
- Some warnings are low priority. Use judgement.
Make it part of your test plan
- Upload your build and read the report the same day.
- Fix crashes and serious accessibility issues.
- Ship the fix to your closed track before recruiting, or as your first mid-test update.
Pair it with Android vitals and Crashlytics for crashes from real testers.
Frequently asked questions
Can I turn off pre-launch reports?
Yes, in the report settings. Most developers keep them on because they’re free.
Why didn’t a report run for my upload?
Google says reports depend on device lab capacity. Some uploads may not get a report, or may get a partial one.
Does the robot crawler use my real backend?
Yes, it runs your real app. Give it a dedicated test account and keep that account’s data separate.
Sources and how we keep this accurate
Policy facts are checked against Google's own documentation on the date shown above. Google can change requirements at any time, so confirm in your Play Console. Where we give advice or estimates rather than Google's rules, we say so. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.
Need 12 testers? Get them free.
Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.
Start freeKeep reading
Using Android Vitals During Your Closed Test
Add Firebase Crashlytics to Your Closed Test Build
Can Closed Testers Use an Android Emulator?
How to Write a Google Play Store Description That Converts
How to Collect In-App Feedback From Closed Testers
Browse all guides, or see the quick answers, guides and comparisons.