Enhanced Crashlytics Investigation for your Android App
<p>In more than 10 years as an Android engineer, I’ve seen a ton of crashes that were impossible to reproduce or things that are behaving in a non-sense when reading stack traces.</p>
<p>Most of the time, I’ve left things as-is, considering it was something beyond my power. I’m pretty sure <strong>it’s the case for a lot of developers</strong>: you’ve seen a lot of crash reports which made non-sense without knowing what to do.</p>
<p> </p>
<p>Me, when reading obscure stack traces</p>
<p>But thanks to <a href="https://firebase.google.com/docs/crashlytics" rel="noopener ugc nofollow" target="_blank"><strong>Firebase Crashlytics</strong></a><strong> (or any other crash reporting tool)</strong>, we have ways to identify how crashes are happening and in <strong>which conditions</strong>. With the experience, you’ll identify if a crash is worth taking your time on investigations or not.</p>
<h1>The crash </h1>
<p>The more your application and your user base grow, the more issues will happen. It’s important to do prioritization work, as many issues can happen, and you may spend a lot of time investigating the cause.</p>
<p><a href="https://engineering.backmarket.com/enhanced-crashlytics-investigation-for-your-android-app-d0a85a011ca0">Read More</a></p>