Play Console asks for the advertising ID declaration when you target Android 13
You 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.
Fix it fast
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" {} +2Match what you see, then jump to its fix
- 1
Your 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
You 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
- 1
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
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
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:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
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 fixMobile apps
Gradle cannot find com.google.firebase:firebase-analytics-ktx
Required by: project :app
Firebase moved the Kotlin extensions into the main modules and stopped releasing the -ktx modules in July 2025.
2 causes, each with a fixMobile apps
Gradle cannot create LibraryVariantBuilderImpl in a Flutter Android build
Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl
This error appears when the Android Gradle plugin (AGP) cannot run in the Gradle or IDE you use.
3 causes, each with a fixMobile apps
Flutter release build cannot open the keystore: HmacPBESHA256 not available
Algorithm HmacPBESHA256 not available
The keystore is a PKCS12 file protected by a newer algorithm than the Java that is reading it understands.
3 causes, each with a fixMobile apps
Android install error: the package conflicts with an existing package of the same name
The package conflicts with an existing package by the same name
Android allows only one app per application ID, and an update must be signed with the same certificate as the installed version.
3 causes, each with a fixMobile apps
Android resource linking fails with resource android:attr/lStar not found
error: failed linking references.
The lStar attribute exists only from Android API 31.
2 causes, each with a fix