Are reported mobile app crashes in Dynatrace referring to fatal crash?

[mengsuan_koe1]

Hi!

Just wondering, when Dynatrace reports a mobile app crash, does that mean that the app has closed from the user's perspective? Or crashes can just mean exception(s) being encountered?

[Thomas_Wirth1]

In Dynatrace, the term "crash" refers to a fatal error that terminates the application. Currently Dynatrace does not distinguish between user perceived and non-user perceived crashes. There a slight differences between the platforms Android and iOS and how "crashes" are handled for crosspatform frameworks. Normally these differences are not relevant.

Example of a non-user perceived crash, the Android OS can start the an application in the background and if that application is terminated by an error, Dynatrace will report it as a crash.

Errors, exceptions and other problems that are handled by the application itself are not automatically monitored by Dynatrace and you have to report them manually:
Android: https://docs.dynatrace.com/docs/platform-modules/digital-experience/mobile-applications/instrument-a...
iOS: https://docs.dynatrace.com/docs/platform-modules/digital-experience/mobile-applications/instrument-i...

[mengsuan_koe1]

I thought so too, that crashes indicate fatal error that terminates the application. However from the user journey, it can be observed that there are subsequent user actions after the app crash. Not sure if it has anything to do with MAUI framework for my case.

Given that there is this suspicion that certain app crash does not terminate the application, I'm also wondering if there is a way to exclude certain exceptions from being regarded as app crash.

[matthias_hochri · Accepted solution]

For MAUI there is also the option to manually report crashes. So it is up to the customer when using those APIs. Additionally in MAUI iOS we are observing AppDomain.CurrentDomain.UnhandledException and TaskScheduler.UnobservedTaskException. If those are signaling an exception we report a crash.