Guides
Straight answers to the Play Console problems that cost weeks
Written for developers who are mid-rejection, mid-review or mid-closed-test — the situations where Play Console’s own documentation stops being enough.
Subscribe by RSSHow to Get SHA-1 and SHA-256 Fingerprints for Firebase and Google Sign-In
Debug keystore, release keystore, and the Play App Signing certificate are three different fingerprints. Using the wrong one is why Google Sign-In fails only in production.
Read the guideEvery Google Play Graphic Asset Size (Icon, Feature Graphic, Screenshots)
One reference for every image Play Console asks for: exact pixel dimensions, format rules, safe zones and the mistakes that get assets rejected at upload.
The Google Play Data Safety Form, Section by Section
The Data Safety form is where most first-time publishers stall. A plain-English walkthrough of every section, the answers that trigger review, and how to stay consistent with your privacy policy.
App Rejected for a Missing or Invalid Privacy Policy? Here Is the Fix
A privacy policy URL that 404s, sits behind a login, or contradicts your Data Safety form is one of the fastest ways to fail Play review. What Google actually checks, and how to satisfy it.
Google Play's 14-Day Closed Testing Requirement, Explained
Personal developer accounts must run a closed test with 12 testers for 14 continuous days before applying for production access. Here is exactly how the rule works and where developers lose weeks.