In the pre-launch report, start with one crash
Check whether a crash hits launch, login, or your main path in review notes. Do not resubmit the same build until that kind of crash is handled.
Play’s pre-launch report runs your build on a pool of devices. It is not proof of approval, but a build that crashes on launch is not worth resubmitting as-is.
Which line to read first
- Does the crash happen on cold start, login, or the main path you described in review notes?
- Does the stack trace match the versionCode you are submitting—not an older build’s crash.
- One obscure device failing vs every device failing: different priority. Fix the “nobody can open it” case first.
- After fixing, bump versionCode and upload again. Do not hammer Submit on the same build.
Goee can translate one crash line from the report into a stop-or-go call. Fixing code is still your engineering team. No crash does not guarantee approval.
FAQ
Q: The report is slow—can we submit to production first?
A: Do not submit while launch crashes are unaddressed. Waiting for the report is not the goal; clearing main-path crashes is.
Q: Apple has no equivalent report?
A: Apple uses crash logs and TestFlight. If the main path won’t open, fix before resubmit. See TestFlight.