App Store Connect crashes not appearing in Xcode/Firebase

Question

Created 14h

Replies 1

Boosts 0

Participants 2

Hi Apple Team,

We have high crash counts in App Store Connect > App Analytics > Crashes (197), but zero matching crashes in Xcode Organizer or Firebase Crashlytics for the same app version/build.

App details:

Bundle ID: com.youtunein.youtunein
Version: [1.88,1.89,1.90,1.91]
Affected iOS versions: [1.88,1.89,1.90,1.91]

Steps tried:

Downloaded raw .crash files from App Store Connect and symbolicated in Xcode Organizer – no crashes appear.
Firebase console clean, no spikes.
dSYM files uploaded via Xcode Archive/Transporter.
Enabled crash reporting in app (no custom crash handling blocking).

Crash reports attached (top 3 symbolicated). No ANRs/symbolication issues visible. Production + TestFlight both affected?

Need help understanding discrepancy and resolving. Thanks!

Boost

Answer 1

DTS Engineer OP

Apple

12h

Thanks for the very interesting post.

Experiencing discrepancies between crash reports from App Store Connect and other tools like Xcode Organizer or Firebase Crashlytics can be frustrating.

If using Firebase Crashlytics alongside Apple’s built-in crash reporting, ensure there are no conflicts. Consider disabling one to see if crash reporting aligns with the other tool. Ensure that the correct dSYM files were uploaded for each build version. Mismatched or missing dSYMs can prevent proper symbolication. Check the build logs or archives in Xcode to confirm that dSYMs were generated successfully and uploaded. Use on the dSYM file to ensure it includes UUIDs matching those in the crash logs. Confirm that no third-party libraries are missing their dSYMs or are causing symbolication issues.

During your testing, have you been able to reproduce the crash? Is the crash reported as terminated by the user?

I would personally disable the third-party crash library to observe the results. However, this is merely my personal opinion. I am aware that handling crashes has been a significant point of contention and has been discussed in various threads. I recommend reviewing previous posts from other developers to understand their approaches to handling crashes.

Nevertheless, I believe the most effective method is to reproduce the issue on your test devices. And I look forward to other developers opinions as well.

Albert Pascual   Worldwide Developer Relations.

0