POST_NOTIFICATIONS on Android 13+: What It Means for Your Listing

Since Android 13 (API 33), POST_NOTIFICATIONS became a runtime permission instead of a manifest-only one, which means your app now needs an explicit user prompt rather than automatic notification access. This doesn't directly change your Data Safety form, but it does affect your listing's described functionality and your target SDK compliance.

Apps still targeting an SDK below 33 without accounting for the runtime prompt commonly see notifications silently fail after upgrade, which shows up as user complaints rather than a Play rejection — arguably worse.

The fix

Fix: confirm your notification permission request flow explicitly, don't rely on manifest declaration alone once you target SDK 33+.

The same check runs automatically when you upload your bundle to the AAB analyzer — permissions, SDK fingerprints, and version info in one pass, free.

Keep going

Data Safety generator →

Turns these answers into a Play-ready CSV.

Data Safety guide →

The full method behind the checks.

Short, specific submission fixes.

Run this check on your own AAB

Free analysis, exports when you need them.

Start free See pricing