Reputation: 2019
So we were about to submit our app for review but we were stopped by Google's new requirement for apps targeting Android 13 and above, which basically tells developers to disclose the purpose of AD_ID
permission in their app. The thing is, our app doesn't declare the AD_ID
permission explicitly, but it turns out some play-services lib or Firebase uses it and thus, it has been merged to our app's manifest.
So I found some solutions so that a permission declared by a library will not be merged to an app's manifest, but my fear is that our app's functionality that depends on Firebase might stop working. Has anyone faced this situation?
Upvotes: 8
Views: 3756
Reputation: 81
If Play console shows the AD_ID
issue, then you can directly fill up the form as "Yes
" and mark "Analytics
" option, if the AD_ID is coming from Firebase Analytics.
if you want to check from where this permission is coming in merged manifest then in Android studio go to Options->Code->Analyze Code->Dependencies..
or just run ./gradlew app:dependencies
in terminal, search "play-services-ads-identifier
" you will get from where this is coming.
if you want to disable to collect the advertising Id, mention the below in Android Manifest file.
<meta-data android:name="google_analytics_adid_collection_enabled" android:value="false" />
Some Google libraries use AD_ID internally. If you don't use any advertising in your app, you can add this to your manifest & the warning will be gone on your next release.
<uses-permission android:name="com.google.android.gms.permission.AD_ID" tools:node="remove"/>
Upvotes: 0
Reputation: 622
If you've disabled collection already, removing the AD_ID permission is unlikely to cause problems. See: https://github.com/firebase/firebase-android-sdk/issues/2582
Disable collection:
<meta-data android:name="google_analytics_adid_collection_enabled" android:value="false" />
Remove permission:
<uses-permission android:name="com.google.android.gms.permission.AD_ID" tools:node="remove" />
Upvotes: 11