Proguard:
-assumenosideeffects class com.google.android.gms.dynamite.** {}
Gradle:
all*.exclude group: 'com.google.android.gms', module: ''
It didn't help in any ways as the dynamite package is still there.
My question is very simple, how do I disable this to be not only GDPR compliant and offer the same quality to countries outside of EU.
I've created a question on stackoverflow, but received no answer. https://stackoverflow.com/questions/62082042/how-to-get-rid-of-googles-dynamite-measurement-in-apk
Hi there,
Thank you for reaching out to us.
You may check out the user tracking-related topics from the standalone version of the AdMob SDK here, which should also be applicable to the Firebase version. In particular, you can request consent from EU users for GDPR compliance, tag ad requests for child-directed treatment for COPPA compliance, and restrict data processing for CCPA compliance.
As for your concern over the GMS Dynamite package: I'm afraid that this package is technically outside the scope of the AdMob SDK (since it is more related to Google Mobile Services in general than AdMob). I would encourage you to seek further assistance for this particular concern on more Android-specific help forums (like StackOverflow).
Regards,
Ziv Yves Sanchez
Mobile Ads SDK Team
Hi there,
Thank you for clarifying your concern.
I'll check in with the rest of the team in order to gather our insights with regards to the GMS Dynamite package. We'll get back to you soon on this.
Hi,
This is Sam from the Mobile Ads SDK support team.
Can you please provide some specific details about the issue you are seeing with your app in terms of behavior related to the Mobile Ads SDK? In particular you have mentioned 'user metrics ... causes ANRs and crashes ...', and also 'communities do not want to install my apps because of this tracking'.
Can you point out which tracking in particular that you and the communities you mention are referring to, and also the ANRs and crashes (examples are fine) that are caused by this tracking?
Sorry for the clarifying question, I just want to ensure we are on the same page in terms of what SDK feature we are talking about here.
Regards
Sam
Hi and thanks for the additional info.
I have reported the ANRs you supplied to the engineering team and we will investigate those as this appears to be unexpected behavior.
With regards to the SDK reporting usage metrics, this feature is a core part of the SDK and cannot be disabled. However, the metrics usage is in compliance with GDPR, AdMob respects the 'Non-Personalized Ads' flag and does not use any data for personalization. Please refer to this article about data handling and this article about Non-Personalized Ads for further information about Googles GDPR policies.
I do recommend however that you delay initialization as per our documentation until you have collected users consent in GDPR countries.
I will let you know when I have updates regarding the initialization ANRs.
Regards
You are free to set non-personalized ads for all users regardless of their location if you choose.
Regarding App Measurement, it can be delayed to start after SDK initialization as per the documentation.
Regards
--
---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads-sdk+unsub...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/nypfS000000000000000000000000000000000000000000000QDMTAE009OqRADAwR4qC2jgRY3u-3g%40sfdc.net.