Disable the Analytics service for Firebase Cloud Messaging

Question

We mirgrated from GCM to FCM without any problems. The notification service is running very well. However, we have to disable the app measurement part of the Firebase Analytics service for legal reasons.

We used this guide to disable the analytics part https://firebase.google.com/support/guides/disable-analytics

So we put this flag to the manifest file:

<meta-data android:name="firebase_analytics_collection_enabled" android:value=false />

and we also disabled the collection programmatically:

FirebaseAnalytics.getInstance(this).setAnalyticsCollectionEnabled(false);

Unfortunately, data is still collected and we can see new events in the Firebase Analytics Console. Is there any possibility to turn off the analytics services completely?

Thanks for your help.

Edit: I also have the deactivation meta-data in the application tag:

<meta-data android:name="firebase_analytics_collection_deactivated" android:value=true />

Answer 1

I tried putting that line in my manifest, inside the application tag, as the first line under the application tag :

 <application
    android:icon="@mipmap/ic_launcher"
    android:name="your.package.name">
    <meta-data android:name="firebase_analytics_collection_enabled" android:value="false" />

When doing so, during the init, Firebase display in the logs:

I/FA: Collection disabled with firebase_analytics_collection_enabled=0

And it seems not to report anything to firebase afterwards.

Answer 2

Just received feedback from the Firebase support team.

The code for manifest file won't compile if you don't add a double quote in the android:value attribute, good job if you've already added that.

Temporarily disabling the analytics collection should work, could you please try to enable the verbose debug option and check the logs?

On the other hand, we are aware that there's an issue with disabling the analytics collection permanently, there's already a bug filed for this and being prioritized by our engineers appropriately. Please keep updated with our release notes for further notice regarding this issue.

We apologise for any inconvenience that this may have caused you, and we appreciate your understanding as we continue to improve our services, moving forward.