Where warnings appear

Notices come from several places. The Publishing overview lists errors and warnings found before submission; Policy status summarises policy issues and progress; the dashboard shows tasks; the developer email receives key notices. Check all four.

LocationPurposeTypical content
Publishing overviewPre-submit checkBuild warnings, missing declarations, version errors
Policy statusPolicy overviewViolation type, deadline, status
DashboardTo-do tasksForms and declarations to finish
Developer emailOfficial noticesReview results, required fixes

Errors versus warnings

Errors block submission and must be fixed, for example missing declarations, version conflicts or an outdated target API. Warnings do not block but should not be ignored: many later rejections start as warnings such as unexplained sensitive permissions or suspicious mismatches with the data safety form.

Fix errors first, then compliance-relevant warnings, then experience suggestions. Save and refresh after each change to confirm the status updates.

Also useful in this topic cluster:

Common violation categories

  • Metadata: names, icons or descriptions with prices, rankings, exaggeration or unsupported claims; misleading screenshots
  • User data and privacy: missing privacy policy, form mismatching behaviour, no account-deletion path
  • Permissions: sensitive access unrelated to core function such as SMS, call logs, all-files access or accessibility services
  • Deceptive behaviour: descriptions not matching function, mimicking system notices, hidden features
  • Restricted content: gambling, financial services or health claims without required declarations or credentials
  • Spam and minimum functionality: templated clones and empty shell apps

Sensitive permission areas (SMS, calls, all-files, accessibility, VPN service) usually need separate declarations and review, so evaluate early whether you truly need them.

Remediation steps

  1. Read the warning and identify the cited policy and data type
  2. Compare with real behaviour: is the description wrong or the feature itself?
  3. Edit the app or listing and ship a new build if needed
  4. Update the privacy policy and data safety form so all three agree
  5. Save in Console and confirm status updates
  6. Resubmit; if you are sure the call was wrong, appeal through the official channel with evidence

Fix everything in one pass rather than probing one item at a time; repeated returns for the same issue lengthen the process.

What not to do

  • Do not switch accounts or package names to re-upload a violating app; associated accounts can be actioned together
  • Do not buy 'guaranteed approval' services — nobody decides for Google
  • Do not invent facts or inflate test size in an appeal
  • Do not request sensitive permissions without explaining the purpose
  • Do not ignore policy emails; deadlines are usually explicit

The dependable path is: read the clause, fix the issue, keep evidence, follow the process.

Extra care for buyers of accounts with apps

If you buy an account with apps, ask for a list of past warnings and takedowns and check the policy status page right after handover. Old violations travel with the account and can affect your new apps.

Put 'any history of warnings?' on the account sheet before buying; a vague answer is a risk signal, so pause. More in the risks-of-accounts-with-apps guide.

Related reading:

Related

Related desks