Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Play Console asks for the advertising ID declaration when you target Android 13

ErrorYou must complete the advertising ID declaration before you can release an app that targets Android 13 (API 33)

Short answer

Play Console wants your declaration to match what the app really does. Look at the merged manifest, not only your own AndroidManifest.xml. If the app uses the advertising ID, the AD_ID permission must be in it. If it does not, find which library added it and remove it.

  • Applies to Android 13 (API 33) and newer, Android Gradle Plugin 8.x, Flutter 3.35
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Find out whether the permission is in the merged manifest of the build you upload. In Android Studio the Merged Manifest tab shows it; from the terminal, search the merger report.

    find . -name "manifest-merger-release-report.txt" -exec grep -n "AD_ID" {} +
  2. 2Match what you see, then jump to its fix

    1. 1Your code or an ad SDK reads the advertising ID, and the grep finds no AD_ID lineThe app uses the advertising ID but AD_ID is not in the manifestFix
    2. 2You never read the advertising ID, yet the merger report shows AD_ID coming from a library manifestThe app does not use the advertising ID, but a library merged AD_ID into itFix

What does the error look like?

  • You must complete the advertising ID declaration before you can release an app that targets Android 13 (API 33)

Cause 1 of 2

The app uses the advertising ID but AD_ID is not in the manifest

1Check

For an app that targets API 33 or higher, Android requires the AD_ID normal permission. Without it the advertising ID is replaced by a string of zeroes. SDKs that declare it in their own manifest add it for you through manifest merging.

find . -name "manifest-merger-release-report.txt" -exec grep -n "AD_ID" {} +

2Fix

Add the permission to android/app/src/main/AndroidManifest.xml, then answer the declaration in Play Console to say the app uses the advertising ID.

<manifest ...>
    <uses-permission android:name="com.google.android.gms.permission.AD_ID"/>
    <application ...>
    </application>
</manifest>

3Verify

Build again and confirm the merged manifest now lists the permission.

flutter build appbundle --release
find . -name "manifest-merger-release-report.txt" -exec grep -n "AD_ID" {} +

Confirmed by developer.android.com

Did this fix it?

Cause 2 of 2

The app does not use the advertising ID, but a library merged AD_ID into it

1Check

Library manifests are merged into yours. The Merged Manifest tab in Android Studio shows where each element came from, and the merger report in the build outputs logs folder records the merge.

find . -name "manifest-merger-release-report.txt" -exec grep -n -B2 -A2 "AD_ID" {} +

2Fix

Remove the element from the merged result with a merge rule marker in your own manifest, and answer the Play Console declaration to say the app does not use the advertising ID. Check that the library you removed it from does not need the ID for a feature you ship.

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="http://schemas.android.com/tools">
    <uses-permission android:name="com.google.android.gms.permission.AD_ID"
        tools:node="remove"/>
</manifest>

3Verify

The merger report no longer shows the permission in the final manifest.

flutter build appbundle --release
find . -name "manifest-merger-release-report.txt" -exec grep -n "AD_ID" {} +

Confirmed by developer.android.com

Did this fix it?

How do I stop it coming back?

  • After adding any analytics, ads or attribution package, open the merged manifest and look for new permissions.
  • Keep one note of which libraries use the advertising ID, so the Play Console answer is a lookup, not a guess.
  • Re-check the merged manifest whenever you upgrade those packages; their manifests change.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Mobile apps

Google Play says the app does not support 16 KB memory pages

check_elf_alignment.sh reports UNALIGNED for a library under lib/arm64-v8a

Google Play requires apps that target Android 15 or higher and ship native .so libraries to run on devices with 16 KB memory pages; from 1 February 2027 it will block updates that do not.

5 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.