Debugging log · Play Console
Can't publish — "App content" declarations incomplete
The AAB uploaded cleanly, the release looked ready, and the publish button was still greyed out — or the review kept coming back "not compliant." The code wasn't the issue at all. Play Console won't release an app until a set of declarations about the app are filled in, and a half-finished one quietly blocks the whole thing. For a first app, this is one of the most common "why can't I ship?" walls.
The short version: the App content section (and Store settings) holds required declarations — Data safety, privacy policy, target audience, ads, content rating and a few others. Any one left incomplete blocks release. Work through the list until every item shows complete.
Where to look
In Play Console, open Policy → App content (and check Store settings). Each item shows a status. Anything not marked complete is a potential blocker, and the dashboard usually surfaces the offending one as a task you must finish before publishing. The fix is rarely hard — it's that these are easy to skip past when you're focused on the build.
The declarations that trip people up
Data safety
You declare what data your app collects and shares, and how it's handled. This must match what your app actually does — including data pulled in by SDKs you added (ads, analytics, crash reporting). A mismatch between your declaration and real behavior is a policy problem, not just a blank form, so answer it against what your dependencies collect, not just your own code.
Privacy policy
Most apps need a privacy policy URL, and it must be a live, reachable page — especially if you collect any data or use ads. A missing or dead link blocks release. A simple hosted page that states what you collect and why is enough to satisfy the requirement.
Target audience and content
You declare the age groups your app targets. If you indicate children are in the audience, a stricter set of requirements and policies kicks in. Answer this honestly — claiming a children's audience you didn't build for creates obligations you'll fail, and the opposite can be a policy issue too.
Ads declaration
If your app contains ads (AdMob counts), you must declare it. Forgetting this while shipping an ad-supported app is a classic mismatch that surfaces at review rather than upload.
Content rating
You complete a questionnaire and Play assigns a rating. Until it's done, the app can't go out. It's quick, but it's mandatory.
These aren't busywork — they're the declarations Google shows users and regulators about your app. Answer them to match reality, including what your third-party SDKs do. The fastest way to fail is to rush them or guess; the fastest way to pass is to fill each one in truthfully and completely.
How to clear it, in order
- Open Policy → App content and note every item not marked complete.
- Finish each one, answering against what your app and its SDKs actually do.
- Add a reachable privacy-policy URL if any item requires it.
- Complete the content-rating questionnaire.
- Return to your release — the publish block tied to those items should now be gone.
Play Console's section names and the exact set of required declarations change over time; the pattern — incomplete declarations block release, and they must match real behavior — is the stable part.