Google Play — Broken or unstable functionality
The reviewer or the automated pre-launch test could not use the app. Google runs your build on real devices before a human ever sees it, so this often comes from the pre-launch report.
What the rejection usually says
Your app does not function as expected — it crashes, force closes, or does not respond.
We were unable to access all or part of your app.
Wording varies between reviewers; the substance does not.
Why it gets triggered
- A crash on a device or Android version in Google's test matrix.
- A login wall with no test credentials supplied.
- A feature requiring a backend that was unavailable during review.
- Permissions denied by the automated tester, leaving the app stuck.
How to fix it
1.Read the pre-launch report first
Play Console shows the exact crash, device and stack trace from automated testing. It usually names the problem outright.
2.Supply working test credentials
Add them under App content, and confirm they work on a clean install. Include any steps needed to reach the gated area.
3.Survive denied permissions
The automated tester declines prompts. Every screen must degrade gracefully rather than hang or crash.
A reply you can adapt
Short, specific, and stating what changed — reviewers read hundreds of these.
Thanks for the report. The crash shown in the pre-launch report is fixed in this build, and we have added working test credentials under App content along with the steps to reach the gated screens.
AppSubmit does this for your app, specifically
Paste the rejection and the decoder reads it against your actual listing, build and release history — then writes the fix plan and drafts the reply. It also watches your submissions, so the next rejection reaches you as a notification rather than a surprise.
Decode a rejection free