How to report crashes using the new Firebase Crashlytics?
See original GitHub issueIn the new version of Firebase Crashlytics the function recordCustomExceptionName:reason:frameArray:
is replaced by recordError
.
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?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Customize your Firebase Crashlytics crash reports - Google
This guide describes how to customize your crash reports using the Firebase Crashlytics SDK. By default, Crashlytics automatically collects crash reports ...
Read more >iOS Firebase Crashlytics not showing up crashes in Dashboard
Launch your app from the home screen to run it without the debugger. Press the “Crash” button to trigger the crash. Run the...
Read more >Crashlytics in the Firebase Console
Once you have Crashlytics up and running in your app, you can navigate to Crashlytics in your Firebase Console underneath 'Quality' and start...
Read more >Using Firebase Crashlytics - FlutterFire
To send report data to Crashlytics, the application must be restarted. Crashlytics automatically sends any crash reports to Firebase the next time the ......
Read more >Crash Report in Firebase Crashlytics - Javatpoint
By default, Firebase Crashlytics automatically collects crash reports for all app's users. We can use Opt-in Reporting by enabling more control over the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Firebase 6.32.0 fixes this issue:
I have bitcode disabled. I’ve now added this script at the end of the build phases
and Crashlytics seems to be able to symbolicate custom Kotlin exception reports.
Using the simple “official” Crashlytics script
"${PODS_ROOT}/FirebaseCrashlytics/run"
doesn’t work since it only uploads the app’s dSYM and not the framework’s one.Does all of this make sense to you?