Sometimes we as developers build the perfect application and feel safe publishing it to production without knowing that some features are failing or giving the wrong output for some reason. But how do we ensure that we are aware of these crashes before our users use our apps? How do we know the extent of the crashes experienced by the users? How do we know exactly where these issues come from, especially in our codebase, so we can fix them?

In this session, I’ll show you how adding Crashlytics to your Flutter app can help you:
- get crash reports,
- identify devices that are crashing,
- track both fatal and non-fatal crashes,
- prioritise issues and fix them.

As a takeaway, you’ll have a deeper understanding of Flutter’s Fatal vs. Non-fatal errors, Crash Reporting with Firebase, Logs, Custom Keys, and Crash Insights.