Firebase-ios-sdk: Crashlytics reports successfully upload but do not appear in the dashboard

[jlaws]

[REQUIRED] Step 1: Describe your environment

• Xcode version: 11.5
• Firebase SDK version:

Installing Firebase (6.26.0)
Installing FirebaseABTesting (3.2.0)
Installing FirebaseAnalytics (6.6.0)
Installing FirebaseAnalyticsInterop (1.5.0)
Installing FirebaseAuth (6.5.3)
Installing FirebaseAuthInterop (1.1.0)
Installing FirebaseCore (6.7.2)
Installing FirebaseCoreDiagnostics (1.3.0)
Installing FirebaseCoreDiagnosticsInterop (1.2.0)
Installing FirebaseCrashlytics (4.1.1)
Installing FirebaseDynamicLinks (4.0.8)
Installing FirebaseFirestore (1.15.0)
Installing FirebaseFunctions (2.5.1)
Installing FirebaseInstallations (1.3.0)
Installing FirebaseInstanceID (4.3.4)
Installing FirebaseMessaging (4.4.1)
Installing FirebasePerformance (3.1.11)
Installing FirebaseRemoteConfig (4.5.0)
Installing FirebaseStorage (3.6.1)

• Firebase Component: Crashlytics
• Component version: 4.1.1
• Installation method: CocoaPods

[REQUIRED] Step 2: Describe the problem

We recently updated to the latest pod version and our crash reports upload successfully but the stack traces do not show up on the website anymore. The issue persists if we disable automatic uploading of the reports.

2020-06-15 13:07:28.747829-0400 Optimize[49305:949032] [Firebase/Crashlytics] Version 4.1.1
2020-06-15 13:07:28.748520-0400 Optimize[49305:949268] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics] Running on iOS Simulator (iPhone), 13.5.0 (19F101)
2020-06-15 13:07:28.752758-0400 Optimize[49305:949263] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics:Settings] Settings expired because build instance changed
2020-06-15 13:07:28.753683-0400 Optimize[49305:949263] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] Root: /Users/joelaws/Library/Developer/CoreSimulator/Devices/62A4D6D0-703B-47E1-A1B3-515B595F83F3/data/Containers/Data/Application/8FEC1164-10CB-4D47-9517-24A69CB7C8A8/Library/Caches/com.crashlytics.data/fitness.optimize.App
2020-06-15 13:07:28.759184-0400 Optimize[49305:949260] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics:Crash:Reports:Event] Registered Firebase Analytics event listener
2020-06-15 13:07:28.759322-0400 Optimize[49305:949260] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] Automatic data collection is disabled.
2020-06-15 13:07:28.759987-0400 Optimize[49305:949268] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics:Crash] 1 unsent reports are available. Checking for upload permission.
2020-06-15 13:07:28.760099-0400 Optimize[49305:949268] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics:Crash] Notifying that unsent reports are available.
2020-06-15 13:07:28.760216-0400 Optimize[49305:949268] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics:Crash] Waiting for send/deleteUnsentReports to be called.
2020-06-15 13:07:31.395699-0400 Optimize[49305:949318] [Firebase/Crashlytics] Packaged report with id '9cb3d0c8b8ab4514b4ba0303b7c56502' for submission
2020-06-15 13:07:31.651099-0400 Optimize[49305:949263] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] Sending unsent reports.
2020-06-15 13:07:31.651219-0400 Optimize[49305:949263] 6.26.0 - [Firebase/Performance][I-PRF300005] URL length exceeds limits, truncating recorded URL - https://firebase-settings.crashlytics.com/spi/v2/platforms/ios/gmp/1:876193183572:ios:bb82d96ca2d883b5/settings.
2020-06-15 13:07:31.651450-0400 Optimize[49305:949263] 6.26.0 - [Firebase/Performance][I-PRF300005] URL length exceeds limits, truncating recorded URL - https://firebase-settings.crashlytics.com/spi/v2/platforms/ios/gmp/1:876193183572:ios:bb82d96ca2d883b5/settings.
2020-06-15 13:07:31.651720-0400 Optimize[49305:949263] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] Image not found
2020-06-15 13:07:31.651825-0400 Optimize[49305:949263] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] Image not found
2020-06-15 13:07:31.651961-0400 Optimize[49305:949263] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] Image not found

... SKIPPING A LOT OF Image not found log messages ...

2020-06-15 13:07:33.802852-0400 Optimize[49305:949323] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] Image not found
2020-06-15 13:07:33.802962-0400 Optimize[49305:949323] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] Preparing the report for the new endpoint: 0
2020-06-15 13:07:33.803068-0400 Optimize[49305:949323] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics:Crash:Reports] Submitting report
2020-06-15 13:07:33.803175-0400 Optimize[49305:949323] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics:Crash:Reports] Submitting async /Users/joelaws/Library/Developer/CoreSimulator/Devices/62A4D6D0-703B-47E1-A1B3-515B595F83F3/data/Containers/Data/Application/8FEC1164-10CB-4D47-9517-24A69CB7C8A8/Library/Caches/com.crashlytics.data/fitness.optimize.App/v5/reports/prepared-legacy/AB4BC7C6-95A3-43D0-8B01-0257C911E0AC.multipartmime
2020-06-15 13:07:33.895122-0400 Optimize[49305:949323] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics:Crash:Reports:Event] Sending event.
2020-06-15 13:07:33.895784-0400 Optimize[49305:949323] 6.26.0 - [Firebase/Performance][I-PRF100009] Recording network trace: https://firebase-settings.crashlytics.com/spi/v2/platforms/ios/gmp/1:876193183572:ios:bb82d96ca2d883b5/settings
2020-06-15 13:07:33.896069-0400 Optimize[49305:949323] 6.26.0 - [Firebase/Performance][I-PRF100009] Recording network trace: https://firebase-settings.crashlytics.com/spi/v2/platforms/ios/gmp/1:876193183572:ios:bb82d96ca2d883b5/settings
2020-06-15 13:07:33.896188-0400 Optimize[49305:949323] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] Settings downloaded successfully
2020-06-15 13:07:33.896410-0400 Optimize[49305:949323] 6.26.0 - [Firebase/Performance][I-PRF100009] Recording network trace: https://reports.crashlytics.com/sdk-api/v1/platforms/ios/apps/fitness.optimize.App/reports
2020-06-15 13:07:33.896517-0400 Optimize[49305:949323] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics:Crash:Reports] completed submission of /Users/joelaws/Library/Developer/CoreSimulator/Devices/62A4D6D0-703B-47E1-A1B3-515B595F83F3/data/Containers/Data/Application/8FEC1164-10CB-4D47-9517-24A69CB7C8A8/Library/Caches/com.crashlytics.data/fitness.optimize.App/v5/reports/prepared-legacy/AB4BC7C6-95A3-43D0-8B01-0257C911E0AC.multipartmime
2020-06-15 13:07:33.948182-0400 Optimize[49305:949323] 6.26.0 - [Firebase/Crashlytics][I-CLS000000] [Crashlytics:Crash] report submission successful

[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.

[morganchen12]

Does the issue go away if you revert back to Crashlytics 4.1.1?

[jlaws]

I checked out the code for the release that we last received crash reports on and force crashed / uploaded reports. It was running Crashlytics 4.1.0. Those reports are no longer showing up either. Our last report was received on May 21st.

One thing to note is that our Crash-free statistics appear correct, but that goes through Google Analytics based on what I saw in the code trying to figure out the issue. As far as I can tell the reports are uploading successfully. Based on the URLRequest with the report actually sending, and the successfully sent message that appears in the log. This is the case for both our older release and latest code.

One thing to note is that it is using the "legacy" endpoint when I step through the code. Should it be using a different one?

[viteinfinite]

It looks to be a generalised issue with Firebase. I'm having the same issue since submitting my app's latest version last week.

[svennnni]

Same issue here. Soft crashes seem to appear in Crashlytics, but no hard crashes. Firebase Analytics shows correct (hard) crash counts.
As a side note: In some other app, hard crashes in Crashlytics started to appear around 10 days after the app update involving a Firebase update (all crashes, even the ones from the last 10 days).

[jlaws]

Since the issue may be on the server side I filed an issue on https://firebase.google.com/support/ where they requested more detailed information about our setup. @viteinfinite @svennnni you might want to do the same to help them narrow down the issue faster. More requests will also raise the priority of the issue to ensure it gets the engineering resources to work on it sooner.

[morganchen12]

The relatively minor changes in recent Crashlytics updates plus the crashes no longer updating for an SDK version that previously submitted crashes successfully indicate this is most likely a server issue, so filing a support ticket is the right way to go.

[svennnni]

Okay, I also filed an issue there. Let's hope they can fix this, on the server at the best, requiring no code updates on our side...

[emilolofsson]

We're seeing the same thing after updating to the latest Firebase Unity SDK (6.14.1). Supposedly there are some changes that completely removes all references to Fabric. I agree it may be a server issue, as we're seeing the same thing on both our iOS and Android apps.

[matthewdanaher]

Having this same issue. Any updates?

[morganchen12]

Closing this since it's too general of an issue to confirm if all the +1's are identical issues or issues with different underlying causes. If your crashes are uploading successfully according to app logs but not displaying in console, please file a support ticket instead.