Introducing crash reports | beta

Introducing crash reports | beta

Vojtech Sibor
Vojtech Sibor (Smartlook Team)  |  Last updated: Nov 5, 2022
1 min read
Take a closer look at session recordings that contain crashes and simplify the debugging process with crash reports.

In addition to tracking crashes, our crash report tool lets you see what happened in the moments leading up to a crash so you can locate and fix bugs easier.

Crash reports enable you to:

  • Review the exact steps that led to a crash
  • Access stack trace reports for quick bug identification
  • Stop having to reproduce crashes manually
  • Increase app stability

Existing crash reporting tools only locate crashes and detect bugs. They don’t tell you why a crash occurred. QA teams must reproduce crashes and report them to developers manually — this takes a lot of time. Our crash report feature displays everything you need to know to fix bugs successfully

Crash reports are primarily made by developers for developers to track crashes accurately. They also enable QAs to ditch the manual crash reproduction process. In other words, crash reports give you more insight into bugs.

If a user reports a bug, you can see what occurred during their session, thanks to their unique ID.

Smartlook’s crash reports feature is currently being beta tested for Android apps. iOS is coming soon. 

Vojtěch Šibor
Vojtěch Šibor

is a Product Marketing Manager at Smartlook. Vojtech is a marketer with product blood running through his veins. He always knows about all the new features and what's coming up. Sometimes he talks about brand stuff and makes sure that the communication is consistent.

0 %