If you need to replicate a user error, you’ll know how difficult it can be to pinpoint the cause. Usually, you’d look at the stack trace or ask the user themselves. However, that’s a lot of guesswork, especially if the stack trace is obfuscated. We’ll show you how to replicate the error faster using Crash Reporting’s Breadcrumbs and the Real User Monitoring Sessions feature.

When developing mobile apps it’s important to monitor errors so that you can understand your user’s experience. You need deeper insight than just a crash report because errors could cause a degraded user experience or a drop in key behavioral metrics. Your team needs to know quickly when there are production problems either with the app itself or with your backend services so you can fix the issue before more customers are impacted.

For most people, crashing means either an application has frozen or entirely disappeared. Sometimes, this is followed by a dialog box asking “Would you like to send a crash report?” Users hit “Send” and move on with their lives, and, most of the time, never think about that moment again. But there is an entire world behind that interaction which is key to driving technology forward.