CODEWITHSUNDEEP
androidandroid-studiogoogle-playgoogle-play-console
Alexandra Nicole
Alexandra Nicole

Reputation: 87

Your advertising ID declaration in Play Console says that your app uses advertising ID error message

So I am trying to upload for testing, and I see this error in Google Play Console:

Error
Your advertising ID declaration in Play Console says that your app uses advertising ID. A manifest file in one of your active artifacts doesn't include the com.google.android.gms.permission.AD_ID permission.

If you don't include this permission in your manifest file, your advertising identifier will be zeroed out. This may break your advertising and analytics use cases, and cause loss of revenue. Learn more

You can remove these errors by updating your advertising ID declaration

Apps that target Android 13 (API 33) without the AD_ID permission will have their advertising identifier zeroed out. This may impact advertising and analytics use-cases. Learn more

So I updated it and selected YES on This includes any SDKs that your app imports that use advertising ID. Also selected Advertising or marketing This is what it looks like

I open up my project in Android Studio, open up AndroidManifest.xml and add this line:

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

When I rebuild, and upload the new app-release.aab file, I still get that same error.

Why do I keep getting this error message? (I know in the "This is what it looks like" part I can select "Turn off release errors", but the message will still be there as a warning.)

Upvotes: 7

Views: 2306

Answers (1)

brAzzi64
brAzzi64

Reputation: 1134

Yeah, this issue can be frustrating because even after updating your manifest, Google Play Console still flags the error. The problem is likely an older app bundle that’s still active on a test track, even if that track is paused. Google Play still considers it “active,” which is why you're seeing the warning.

These are the steps that worked for me:

  1. Go to the App Bundle Explorer in Google Play Console.

    • Select your app and open App Bundle Explorer from the menu.
    • Click Add Filter, select Release status, check Active, and apply the filter.
    • This will show you all the active app bundles. If you see more than one, that means there's an older bundle causing the issue.

  2. Check the tracks where old bundles are still active.

    • Click the blue arrow next to each bundle (except for the one with the highest version code, which is your production version).
    • Under Releases, click Show details to see which tracks the bundle is active on.

  3. Decide how to handle the outdated test track bundles:

    • If you still need the track, just upload your updated production bundle to it.
      • Go to that test track, create a new release, and when prompted to upload, choose Add from library, then select your latest bundle.
    • If you don’t need the track anymore, do an empty release to remove the bundle.
      • Go to the track, start a new release, but don’t upload anything.
      • Name the release something like "Removing bundle" and add a note like "Empty release to deactivate bundle".
      • Submit it for review.

Once those outdated bundles are removed or updated, the warning should go away. Hope that helps!

Upvotes: 3

Related Questions