The crash analytics section is a great section for Product Owners and Developers to stay on top of critical crashes in the app.

 

Tips:

  1. Share any crash issue with your team using the public link.

  1. Integrate Appsee with Crashlytics to send Appsee videos to your Crashlytics dashboard.
  2. Upload dSYM and mapping files to see exactly which line of code is causing the crash.
  3. Set up your video recording settings to ensure you always have a video of crashes.

Appsee aggregates crashes into issues. You’ll get a high level overview of how many issues your app has, how many sessions are crashing, how many users are affected by crashes, and on average how long is there between crashes.

It’s great to review the daily crash graph side by side with your version release dates so you can understand if any new version has caused a peek in crashes.

Developers:

If you click into a crash issue, a new window will open with more information regarding that specific issue. You’ll have access to all of the sessions that experienced this crash. The videos come in handy here, saving your developers valuable time because they no longer need to recreate the issue! If you input your mapping or dSYM files, you will also be able to see exactly which line of code causes the crash.

Product:

The statistics tab can help you understand how to prioritize your crashes. For example, you can look at the session index. This will show you if the user is in their first session, or their 100th session. If the crash is mostly happening to new users, you might want to consider increasing the priority on fixing this crash.  If the crashing screen is on a payment screen or registration screen, this might also be a crash to prioritize.

Recommended Articles:

  1. How to get a symbolicated crash log
  2. Crashlytics integration guidelines
  3. How does Appsee track crashes