LOGS & breadcrumbs view in firebase console are empty

[jesus-mg-ios]

Description

Since 2 days ago I cannot see logs& breadcrumbs in firebase console. I don't know if this is because the SDK or it is because an error on the firebase console. Version 10.25.0

Screenshot

Firebase SDK Version

10.25.0

Xcode Version

15.2

Installation Method

Swift Package Manager

Firebase Product(s)

Crashlytics

Targeted Platforms

iOS, macOS, App Extensions

Relevant Log Output

No response

If using Swift Package Manager, the project's Package.resolved

No response

If using CocoaPods, the project's Podfile.lock

No response

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[rizafran]

Thanks for reporting, @jesus-mg-ios. Our engineers have identified and fixed the issue. Due to our release cycle, we're unable to provide the exact date, but the fix should be released early next week. Apologies for the inconvenience this may have caused you.

[cyonix]

@rizafran Will the fix result in an SDK update?

[rizafran]

@cyonix, I think the fix will be applied on the backend side so it doesn't need an SDK update.

[themiswang]

Hello folks,

Confirmed the issue is fixed on our backend, Gonna close this issue.

[jesus-mg-ios]

@themiswang it still happens. Not for all non fatals errors and crashes, but some of them are empty when I'm sure they don't have to.

[Kal-Elx]

Just as @jesus-mg-ios I also see an empty Logs & Breadcrumbs tab for some error reports that should have data.

Can this issue be reopened?

[sipersso]

Same here. I am also getting the same issue. Interestingly I can see in the dashboard that firebase_screen events are happening including the correct parameters.

[hsoi]

Still happening for me as well.

@rizafran @themiswang curious - given the nature of the problem and the backend fix, should we expect existing entries to start showing logs? or will it only work for new entries that came in after the fix? (I guess it's a wonder if the problem/fix was something cosmetic, the data is there it just wasn't being shown; or if the problem is deeper and there's actually data loss).

What can we do to help get this tracked down and truly fixed?

[rizafran]

Thanks for letting us know about the issue happening again. It seems that our engineers are already aware with the issue and they're currently investigating it. We'll let you know once we have an update.

[tosulc]

Any updates on this one?

[mserougi]

Experiencing the same issue as well.

[samedson]

Hey folks, did some digging into this. Right now I think there might be 2 issues going on.

Issue 1: If generally logs are showing up, but the screen_view Analytics breadcrumbs are not, you may need to check how you are using the Analytics API. The AnalyticsParameterScreenClass should be a string, not a class name.

You'll see a log if you're running into this issue:

10.29.0 - [FirebaseAnalytics][I-ACS013000] Screen parameter value must be of type NSString: CrashlyticsSwiftUIExample.CrashButtonView
10.29.0 - [FirebaseAnalytics][I-ACS031028] Received invalid class for screen: CrashlyticsSwiftUIExample.CrashButtonView

Issue 2: Some folks seem to not see any logs at all, including logs added to Crashlytics via the Crashlytics.log API. If this is the case, we need to dig deeper into what may be a frontend issue by looking at your specific app. If you are experiencing this, please reach out to support and reference this github issue so we can look into your app. We haven't been able to reproduce this.

[google-oss-bot]

Hey @jesus-mg-ios. 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!

[sipersso]

We are still seeing the issue. Reached out to support and was told to update the SDK to the latest version (11.0) before you would help. Will do a release early next week and keep you posted.

[google-oss-bot]

Hey @jesus-mg-ios. 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.

@jesus-mg-ios 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.