Firebase Performance Monitoring Console/Logcat Spam

[findyourexit]

• 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:

1. Followed the official getting started guide for Android to add Firebase Performance Monitoring to my app.
2. Built/ran my app using a physical device deployment target (Pixel 5 running Android 12).
3. 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!

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[argzdev]

Hi @findyourexit, thanks for your report. Unfortunately after testing the same scenario, I'm unable to reproduce this issue. Could you answer a few questions for us to narrow it down?

1. Is there any specific action do you perform before experiencing this issue?
2. Is this issue consistent on every run?

Also any chance you could provide us with an MCVE?
Thanks!

[visumickey]

While we wait on reproducing this, an update is that these messages are coming from the library Firebase Performance uses for event dispatching. We are working with them to figure out ways to having a good logging message.

Reference: https://github.com/firebase/firebase-android-sdk/blob/master/transport/transport-runtime/src/main/java/com/google/android/datatransport/runtime/scheduling/jobscheduling/AlarmManagerScheduler.java#L107

[findyourexit]

Thanks for the super prompt replies @argzdev and @visumickey!

@argzdev - I'll endeavour to produce an MCVE to share here. When/if I can do so, I'll report back right away.

[google-oss-bot]

Hey @findyourexit. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@findyourexit if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.

[ktiniatros]

Hello,

I created a reproducable case: https://issuetracker.google.com/action/issues/225529530/attachments/36592621?download=true

Download, unzip and open the project in android studio and run it on any emulator. You will see the spam in logcat.

Since you are working on this, please remove the logs or ideally make them configurable (be default to not show with an option to enable them).

[jeremyjiang-dev]

@vkryachko Would you like to take a look at this as the logs are coming from the firelog side?

[google-oss-bot]

Hey @findyourexit. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[russellwheatley]

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.

[vkryachko]

@jeremyjiang-dev These logs happen any time an event is scheduled for upload, I think an initial question to answer is whether that's normal for FirePerf to log this much data? It sounds like that should not be the case, can you check if you're uploading more data than necessary?

[jeremyjiang-dev]

Hey @vkryachko ! We have not changed the volume or frequency on our recent SDKs and the QPS looks normal. Is there a way to turn off the Firelog logs?

[tomkulaga]

I wanted to check if, has there been any updates?