Menu
I'm using Crashlytics for crash reporting of my Android app. So far, it's working mostly good except with issue. The one critical issue is that it's missing a few custom logs before the statement where app crash occurred. I want to ask that if there is any mechanism to flush the logs or any other approach to get all the logs reported?
Thanks in advance.
590
To manually upload your dSYMs, you can use the console-based "Drag and Drop" option to upload a zip archive containing your dSYM files (go to Firebase console > Crashlytics > dSYMs tab).
Try forcing a crash, you should see the logs captured before the crash in the crash report. If you want normal logging, you should look into Firebase analytics, it'll help you keep track of regular events and other analytics data.
Crashlytics associates the logs with your crash data and displays them in the Crashlytics page of the Firebase console, under the Logs tab.
Firebase Crashlytics is a lightweight, realtime crash reporter that helps you track, prioritize, and fix stability issues that erode your app quality. Crashlytics saves you troubleshooting time by intelligently grouping crashes and highlighting the circumstances that lead up to them.
This might be one possible of not getting few custom logs..
So what Crashlytics doc say is
Note: By default, Crashlytics currently supports a maximum of 64 key/value pairs. Once you reach this threshold, additional values are not saved. If you need more, please contact Support.
visit Crashlytics Custom Logs
134
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
