BreadCrumbs to enhance your Crashlytics’s experience
Well, must be said that after more than three years using Crashlytics as a crash reporting tool for my Android projects, even with its most basic version, the feature I love the most is its logging tool (breadcrumbs), and after several conversations with different Android Devs some of them haven’t use it yet.
Leaving Breadcrumbs
… and it’s true, I’ve found myself several times looking for cues on big stack traces on some crash reports having no idea on how to tackle them, guessing if a given value was X or Y, then thinking about paths that didn’t happen. And the crash itself doesn’t give us enough information. In these especial cases is when leaving some breadcrumbs can help us to identify easily what the user was doing when the crash happened and it is just using Crashlytics.log function. In that way, we can define an Utility to log that can be used anywhere in the app and will help us to better understand a crash.
How Can It Be Seen?
Anytime you open a crash, you have other tabs to see additional information: logs and keys. To drop some breadcrumbs we used the log from Crashlytics, then in the Logs tab we can see that additional information, usually we log the parameters we send to a given function or to leave a trace to help us better understand some conditions on a given time.
Isn’t it very cool? for sure this single tip/tool can help us to give more accurate solutions to our users.
See you soon on a new helpful article to improve our development process.
