Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Firebase Performance Monitoring Console/Logcat Spam
See original GitHub issue- Android Studio version: Android Studio Bumblebee | 2021.1.1 Patch 1 (Build #AI-211.7628.21.2111.8139111)
- Firebase Component: Firebase Performance Monitoring
- Component version:
com.google.firebase:firebase-bom:29.1.0(com.google.firebase:firebase-perf:20.0.5,com.google.firebase:perf-plugin:1.4.1)
Steps to reproduce:
The steps to reproduce this were rather simple. To reproduce, I simply:
- Followed the official getting started guide for Android to add Firebase Performance Monitoring to my app.
- Built/ran my app using a physical device deployment target (Pixel 5 running Android 12).
- Watched Logcat/console and observed the same two lines (with very minor variation) appearing over and over again, without end.
The two rows that keep appearing are as follows:
2022-02-14 16:17:49.179 25682-25745/com.redacted.app.redacted.dev D/TransportRuntime.SQLiteEventStore: Storing event with priority=DEFAULT, name=FIREPERF for destination cct
2022-02-14 16:17:49.182 25682-25745/com.redacted.app.redacted.dev D/TransportRuntime.JobInfoScheduler: Upload for context TransportContext(cct, DEFAULT, MSRodHRwczovL2ZpcmViYXNlbG9nZ1luZy1wYS5nb59nbGVhcGlzLmNvbS92MS9maXJlbG9nL2xlZ2FjeS9iYXRjaGxvZ2xBSXphU3lDY2traUg4aTJaQVJ3T3MxTEV6RktsZDE1YU3HOG96S28=) is already scheduled. Returning...
As mentioned, the above rows continue to appear over and over, with approximately less than a second between each occurrence.
I’ve found loosely related posts on StackOverflow and on other projects here on GitHub, but no resolution seems apparent.
In order to pre-empt the recommendation to disable logging via AndroidManifest.xml firebase_performance_logcat_enabled meta-data, I’ve already done so, however it doesn’t stop the above from occurring:
<meta-data
android:name="firebase_performance_logcat_enabled"
android:value="false" />
Any help with this would be greatly appreciated!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:13 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hey all 👋 , I thought I would chime in to let you know that this is an issue for a number of users in FlutterFire which thinly wraps around this SDK. It does appear to be an intermittent issue, but a very real one.
For another possible, reproducible sample, see here.
I wanted to check if, has there been any updates?