Firebase-ios-sdk: FR: allow sending unsymbolicated stack traces in custom exception models.

[barakwei]

Feature proposal

• Firebase Component: Crashlytics

This is in continuation to #4706 where I describe our use case in length.

First of all thanks for adding [FIRCrashlytics recordExceptionModel:] it will help us a lot. My problem with the current API is that in order to create the stack trace inside the exception model, I must use the [FIRStackFrame initWithSymbol:file:line:] method, so my stack trace must be symbolicated. As you know, we usually don't have symbols in production, so I would like to ask if the [FIRStackFrame stackFrameWithAddress:] can be made public, that way I could send my own unsymbolicated stack traces, which can be done now with the Fabric SDK.

[samedson]

Thank you for the feedback and info! Have a couple quesions:

• How do you construct the unsymbolicated stacktrace?
  
  
  
  • Are you using NSThread's callStackReturnAddresses? This is what the recordError API uses to construct stacktraces
  
  
• Do you find that the constructed stacktraces are successfully symbolicated in the Crashlytics backend?

[barakwei]

NSThread gives you the stack of the current thread. We use low level API to walk the stack of other threads and "manually" build the stacktrace.
The sent stacktraces are symbolicated in the backend.

[Thomas-Vos]

In the old Crashlytics, recordCustomExceptionName is used by CrashKiOS to report exceptions in Kotlin code to Crashlytics.

The Kotlin framework generates a Kotlin exception which contains a stack trace. This exception and its stack trace are uploaded manually to Crashlytics. For more information see: https://github.com/touchlab/CrashKiOS

In the new Crashlytics it is not possible to record unsymbolicated stack traces. Could [FIRStackFrame stackFrameWithAddress:] be made public?

[samedson]

Ok thanks for the feedback folks. We'll work on addressing this in FIRCrashlytics.

[viteinfinite]

Hi @samedson, thank you for taking care about this!
Do you have an update? Fabric should be closed now (well, it actually isn't) and this feature is still not implemented :(

[jiehu5114]

mark

[HJTXX]

mark

[ChenMengqi]

Still don't have this API

[Thomas-Vos]

Hello @samedson, I just received an email that we need to use the latest Firebase Crashlytics SDKs before November 15, 2020. Unfortunately I cannot migrate to the new SDK yet as this feature has not been made public. Do you have an update about this?

[elenadoty]

We've added this API to a branch that should be going out in the next release.

[paulb777]

Marked with the 6.32.0 - M79 milestone

[barakwei]

Thanks for making this work.