firebase-android-sdk: Firebase Analytics google_analytics_automatic_screen_reporting_enabled not working
Environment
- Android Studio version: 4.1.1
- Firebase Component: Analytics
- Component version: 18.0.0 ( using bom:26.1.0)
Steps to reproduce:
I added meta-data google_analytics_automatic_screen_reporting_enabled to false in AndroidManifest.xml to disable screen view event. Yesterday screen_view was not sent as I expected but today with the same codebase, it’s keep sending screen_view event. I checked on logcat using adb logcat -v time -s FA FA-SVC) as well as DebugView.
Relevant Code:
<meta-data
android:name="google_analytics_automatic_screen_reporting_enabled"
android:value="false" />
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 37
- Comments: 56 (1 by maintainers)
Hello to all,
The new version of Firebase Bom: 28.0.1 containing the Firebase Analytics: 19.0.0.0 version correctly disables the automatic screen_view event that we want to remove.
Here is the data collection for the last 30 min:
It seems to depend on particular device or system version.
I created a simple Android TV app that lets you test if automatic screen reporting is disabled: https://github.com/piotr767/firebase-analytics-test. You just need to paste the google-services.json for your Firebase project.
When I run it on Android TV emulator with API 28 image it works correctly (no automatic screen events are reported) but when I run it on my physical Android TV device with API 28 it doesn’t work (all screen events are reported). I saw it working correctly on my physical device about a month ago though.
@eburley are there any system settings / configs that can affect this option?
Also wondering what happened here. I’m glad the issue seems to be fixed, but I’d like the peace of mind to know the issue was specifically identified, reproduced and fixed. Otherwise I worry about it randomly starting to happen again
Hi, Do we have any updates about this issue? Thanks
Still the same issue with
19.0.1.Our team is looking into the issue now
@allenktv any news about that ? This is a huge blocker for us
Can confirm, the issue still exists.
We are looking into this issue and have a potential fix going out in the next release (Aug 5). I would suggest updating to the latest version of the SDK once it releases, and seeing if the issue persists.
Hi all, I checked the DebugView today and I am no longer seeing any automatic screen events, only the ones I manually track 🎉 .
I didn’t update the SDK and still using
com.google.firebase:firebase-bom:28.3.1Apologies for the miscommunication, there were issues on our end and the potential fix will instead be out on the next release, scheduled for August 19th.
I’m having this problem with
com.google.firebase:firebase-bom:28.1.0The potential fix has been released. Please download the latest version to see if the issue has been resolved. Thanks!
Looks like there was no Android release yesterday. Any new ETA?
I assume this issue has a somewhat high priority for many of us, cause it basically breaks the manual screen tracking.
I’m not sure what the general impact of this bug is, but I can report that it’s a significant problem for a Flutter app that does its own screen reporting. Any native plugin that presents an Activity causes the reported screen class to change, which breaks our system.
@ersen-lw I did the same check in Firebase Analytics and filtered the
(for some reason the header of the column is always Screen class)
*I used the version numbers from the Crashlytics Operating system filter
firebase-bom:26.7.0
screen_viewevents on OS with version. All versions* had (not set) values.