Android AD_ID
We've had a few user complain of issues with declared privacy settings and permission on google play.
We did some digging and found that our code for forcing removal of the AD_ID didn't quite work as expected.
We've fixed that but have found that there's still an ad-id issue we might have.
If you include admob, the Ad Identifier package will be installed by default.
If you declare an app child directed, we include the appset package (which lets admob access ad id but only with a given set of apps. Basically allowing cross promotion within your own apps, but not with other apps).
My gut says even this is undesirable with child directed apps, but I'm not going to blanket remove it without testing since I'm not 100% sure it can be removed safely.
We'll update you more next week, but for now if you did not intend to allow AD_ID permissions, please republish your android app.
Comments
Thanks for the heads up. One quick question, though: I was going through the google updated policy here: https://developers.google.com/terms/api-services-user-data-policy#:~:text=You%20must%20disclose%20all%20user,a%20third%20party%20conducting%20surveillance. and was wondering whether this will affect the way platform login is implemented in play games services. It mentions specifically:
Child-directed apps: If your application is directed primarily at children, it should not use Google Sign-In or any other Google API Service that accesses data associated with a Google Account. This restriction includes Google Play Games Services and any other Google API Service using the OAuth technology for authentication and authorization.
Mixed audience apps: Applications that are mixed audience shouldn't require users to sign in to a Google Account, but can offer, for example, Google Sign-In or Google Play Games Services as an optional feature. In these cases, users must be able to access the application in its entirety without signing into a Google Account.
Are we expecting some updates on this?
Sorry, we've been heads down on some other fixes. I'll try to get this sorted this week.
To answer your question @C. Victory, no change. The platform login is a behavior, so it's up to the user to handle his.
Awesome! Thank you for the clarification.
@adent42 Hello, I received a policy violation notice requiring me to remove the Advertising ID from my game. However, despite unchecking the AD_ID permissions box in the "Extra Permissions Required" section of the Gamesalad publish page and checking the app child-directed box, the generated aab file still includes the AD_ID permission. Refreshing the Gamesalad publish page, resets the permissions box back to checked.
Am I doing something wrong or missing something? I appreciate any help or insights you can offer.
@adent42 Hi, what is the solution to this problem? I have the same issue and I see that the error has been around for a couple of months. Thanks in advance.
Use Build RC again. We fixed the issue for @geoascencio recently. Because it was a process fix and not a build fix (i.e. it was something in our build script and not in the engine version), I forgot to announce the fix.
ok thanks, I'll try
I have used Build RC
But the same error as @geoascencio will occur
Please tell me how to solve it?
Can you send me your publishing link?
Any update on this AD_ID issue? I’m facing the same issue here and I can’t update my apps…
thanks(:
@nir312, the issue should have been resolved a while ago, let me ping you via messaging.
Oh ok, great.
because I tried to update my app and I get this error for some reason..
also the buttons are not working for the Build RC on iPhone
@nir3112 can you send me an publishing link. The buttons being stuck is usually a sign of a stuck build so I can try to unstick it for you.
Thanks(:
I sent it to you via message
I'm having an issue where I'm missing the AD_ID permission when it should be included. This is the message I've received from Google when uploading the build:
Can you DM me your publishing link?
@adent42 - I've just looked at my publishing settings and noticed there's a AD_ID Permissions checkbox, which I currently have unchecked.
I'm guessing this may be my issue, should this now be checked when we publish and use Admob in our apps?
Yes, unless you're targeting kids apps.
Thanks, the AD_ID Permissions checkbox has fixed this issue.
However I do now have another Google Play issue with Foreground Service Permissions. I've started a new thread on it here:
https://forums.gamesalad.com/discussion/99095/google-play-publishing-issue-foreground-service-data-sync#latest