Google Play broken Functionality policy: fixes and checks

A Broken Functionality rejection means the submitted app doesn’t behave as a working app should. Start with the reviewer’s device, steps, and screenshot rather than assuming your development build proves it works.

What to check

Install the release artifact through a test track on a clean device. Check startup, authentication, permissions, API configuration, and production-like backend access without using a developer session.

Review crashes and freezes by Android version. Include denied permissions, poor connectivity, empty accounts, and expired sessions. A login failure caused by missing reviewer credentials can look like a broken app.

How to address the rejection

Fix the failing path and submit the corrected build, or provide working access if the build itself was sound. Keep review credentials and necessary services available.

Record the same steps on the corrected version and identify the version code in your response. A local simulator recording from a different build doesn’t demonstrate that the rejected artifact’s problem is resolved.