I could really use the data from Crashlytics. It'd be useful to triage, mute, analyze, and resolve fatal and non-fatal exceptions from my phone.
Ran Van commented
I had often neglected such crashes in my earlier developer days. But I think, we should at least know the point of origin of such crashes. Maybe this would help us track down the crash, or if not, then, at least we can know the severity of this, by understating that this did not popped up in the applications major flow.
Custom keys help you get the specific state of your app leading up to a crash. You can associate arbitrary key/value pairs with your crash reports, viewable right from the Fabric dashboard.
It’s often useful to have some context recorded about the events leading up to a crash. Crashlytics provides logging facilities to make this easy. These messages are associated with your crash data and are visible in the Fabric dashboard if you look at the specific crash. Like https://passwordrecoverys.com https://passwordrecoverys.com/