Solving the Families Policy Requirement Rejection in Android PlayStore
<p>A recent challenge many Android developers have faced is the consistent rejection of apps from the PlayStore, particularly concerning the “Families Policy Requirement.” This policy insists that apps targeting children must not transmit specific identifiers, including Android advertising identifier (AAID), SIM Serial, Build Serial, and more.</p>
<p>The problem faced by many developers, including us, was that the solutions available were often not sufficient to meet Google’s requirements, leading to back-and-forth communications and repeated rejections. In our case, we stumbled upon an unexpected connection between this requirement and the Facebook SDK.</p>
<h1>The Challenge</h1>
<p>One of the dependencies which automatically includes the ads permission is from Firebase refer to this release notes: https://firebase.google.com/support/release-notes/android#analytics_v20-1-1</p>
<p>Unfortunately, it will cause an issue that we facing according to this policy guideline :<br />
https://support.google.com/googleplay/android-developer/answer/6048248</p>
<p>So we remove the permission from our AndroidManifest by adding these lines:</p>
<pre>
<uses-permission
android:name="com.google.android.gms.permission.AD_ID"
tools:node="remove" /></pre>
<p>Despite removing the permissions for AD_ID, our app was still being rejected. Even after double-checking the Gradle dependency trees for any suspicious ad-related dependencies, we couldn’t find the culprit.</p>
<p><a href="https://herisulis.medium.com/solving-the-families-policy-requirement-rejection-in-android-playstore-5bba0a953c7d">Visit Now</a></p>