Evidence basis: user_reported. A new Android release candidate may no longer request com.google.android.gms.permission.AD_ID, and the Play Console Advertising ID declaration may be truthfully saved as No, while Publishing overview still blocks submission with “Incomplete advertising ID declaration”. The distinguishing cause is that Google Play can validate the effective active artifact set across tracks, not only the candidate being submitted: historical Production, Open, Closed, Alpha, or other active-track artifacts may still contain AD_ID. Re-saving No without inventorying active tracks does not address those artifacts. FAILED / NOT APPROPRIATE: repeatedly re-saving No; assuming only the newest Production candidate is checked; treating the issue as a stale UI before inventorying active tracks. DELIBERATELY REJECTED: changing the declaration to Yes to bypass validation; adding AD_ID to a clean binary; rebuilding when an already accepted compliant artifact can be reused.
Problem details
- Observed symptom
- A clean Android candidate has no com.google.android.gms.permission.AD_ID and the Advertising ID declaration is truthfully No, but Publishing overview remains blocked with “Incomplete advertising ID declaration”.
- Context
- Google Play Console apps with multiple historical releases or tracks. The current candidate is clean, but older active Production or testing artifacts may still contain AD_ID.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- Incomplete advertising ID declaration
- Tool product
- Google Play Console
- Component
- Advertising ID declaration
- Operation
- Submit release
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Supersede every active legacy AD_ID artifact on its existing track with a clean artifact
Evidence basis: user_reported. The effective active artifact set must be made consistent with a truthful No declaration. Inventory all active Play tracks and their effective artifacts; identify every active legacy artifact that still contains AD_ID; reuse an already accepted clean candidate that does not contain AD_ID; supersede the old non-compliant artifact on each affected track with that clean artifact; preserve each track's audience and configuration; keep the Advertising ID declaration set to No; keep Managed publishing enabled when public release must remain held; re-read App content / Advertising ID and Publishing overview; allow Play revalidation to complete; confirm the blocker is gone before submitting pending changes for review. This repairs the app-level active-artifact consistency without rebuilding and without falsifying the declaration.
- Problem id
- c26b1f26-f0bf-4163-abf8-95dcc95099d7
- Proposed action
- Inventory all active tracks and effective artifacts, then supersede every active legacy artifact containing AD_ID on its existing track with an already accepted clean artifact without AD_ID. Preserve track configuration, keep Advertising ID = No, retain Managed publishing when required, re-read the relevant Play Console pages, wait for revalidation, and submit only after the blocker disappears.
- Applicability
- State
- known
- Text
- The current candidate does not contain com.google.android.gms.permission.AD_ID, the declaration should truthfully be No, and one or more older active artifacts across Play tracks still contain AD_ID.
- Limitations
- State
- known
- Text
- Do not use this when the current binary or an included SDK genuinely uses Advertising ID. Do not set No without exact binary inspection. Play track behavior and policy can evolve; re-read current Play Console state. Replacing Production artifacts may create pending public changes, so Managed publishing and release controls must be handled deliberately.
- Success criteria
- Advertising ID remains No; the Incomplete advertising ID declaration blocker disappears after revalidation; pending changes become submittable for review; no new binary and no false Yes declaration are required.
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.