New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to report crashes using the new Firebase Crashlytics? #3
Comments
Related: firebase/firebase-ios-sdk#5182 |
mark |
Firebase 6.32.0 fixes this issue: class CrashlyticsCrashHandler: CrashkiosCrashHandler {
override func crashParts(
addresses: [KotlinLong],
exceptionType: String,
message: String
) {
let exceptionModel = ExceptionModel(name: exceptionType, reason: message)
exceptionModel.stackTrace = addresses.map {
StackFrame(address: UInt(truncating: $0))
}
Crashlytics.crashlytics().record(exceptionModel: exceptionModel)
}
} |
I've tried it but I get a "(Missing)" label instead of the correct "file + line" label related to an exception raised from the Kotlin/Native "shared" framework, and I'm quite confident that the related dSYMs have been correctly uploaded to Firebase Crashlytics; any idea? |
@matteobianchi3 Did you upload the dSYMs from App Store Connect as well (if you are using bitcode)? |
I have bitcode disabled.
and Crashlytics seems to be able to symbolicate custom Kotlin exception reports. Using the simple "official" Crashlytics script Does all of this make sense to you? |
Looks all right I think, it is similar to what is mentioned in the CrashKiOS readme: https://github.com/touchlab/CrashKiOS#upload-dsyms-to-crashlytics I have the script that is mentioned in the readme in my project as well. |
closing this for now. We have explicit support in Kermit for adding Crashllytics. You don't have to use it but can see how we do it there. |
In the new version of Firebase Crashlytics the function
recordCustomExceptionName:reason:frameArray:
is replaced byrecordError
.See the following: https://firebase.google.com/docs/crashlytics/upgrade-sdk?platform=ios#recordcustomexceptionnamereasonframearray_is_replaced_by_recorderror
The alternative appears to be one of the following:
The ExceptionModel can be created using a name, reason, and stackTrace. This looks like the way to go but I cannot find a way to create a StackFrame using an address. The StackFrame only has a constructor for symbol, file, and line. Any ideas how to report the exception to Firebase now?
The text was updated successfully, but these errors were encountered: