Skip to content

Crashlytics doesn't symbolicate standard libs from watchOS SDK #6672

Closed
@markvasiv

Description

[REQUIRED] Step 1: Describe your environment

  • Xcode version: 12.0
  • Firebase SDK version: 7.0.0
  • Firebase Component: Crashlytics
  • Component version: 7.0.0
  • Installation method: CocoaPods

[REQUIRED] Step 2: Describe the problem

After @jostster introduced watchOS support for Crashlytics in #6262 and #6436, I've been really eager to try it out with our watchApp. I managed to integrate Crashlytics, force a crash and upload it to Firebase 🎉

The issue is that while my code is symbolicated, standard libraries are not, and I wonder if that's an issue on my side or something that can be fixed on Firebase backend side. If I'm not mistaken DSYM that I upload contains only symbols for my app, and symbols for iOS SDK libs are collected and then used for symbolication by Firebase. I guess that DSYMs for watchOS SDK libs are not handled as of now, but I really hope it can be fixed.

Steps to reproduce:

  1. Integrate Crashlytics to watchApp
  2. Do [FIRApp configure]
  3. Force a crash (exception)
  4. Upload DSYM
  5. Check crash report in Firebase console
  6. Notice that app code is symbolicated, and WatchKit code is not

Screenshot 2020-10-05 at 18 41 46

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions