Crashlytics doesn't symbolicate standard libs from watchOS SDK

[markvasiv]

[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

[samedson]

@markvasiv thank you for the feedback here. We need to update our process to include these symbols in backend now that watchOS is starting to be supported.

I'll let you know when we take on the work to get these symbols included.

[markvasiv]

Hey! Do you have any updates on this issue or possible timeline you could share?
@samedson @elenadoty

[samedson]

Hey @markvasiv, we don't have a timeline to support this for watchOS right now. One of the things that makes this hard for us is the restore images for watchOS are not listed in the same way as the other Apple OSs, so we need to pick up a good amount of work to get it working. When we take on fully supporting watchOS, we'll likely pick up this work.

[CatStudioApp]

It looks like iOS SDK cannot be symbolicated as well.

[themiswang]

Close this issue because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem.