Feature Request
Indicate in the report if an error resulted in a crash or not
gshackles
When looking through our error reports it can be difficult to determine whether a particular error report resulted in an app crash or not. Errors that we manually send are easier to reason about, but it's not always that simple. For example, Raygun catches TaskScheduler.UnobservedTaskException which are important to know about but do not necessarily result in an app crash.
Can this be added as a standard piece of information for the Xamarin.iOS/Android providers?
Raygun
Jason Fauchelle
Posted on
May 26 2014
Hello
I do not know of any reliable way to detect whether or not an exception causes the application to crash. If you know a way, we would love to hear it. (Or open a PR on GitHub: https://github.com/MindscapeHQ/raygun4net)
What you could do is add this information as a custom tag. The Send method has overloads to send a list of tags. If you send the exception in a try/catch block, you can send a "non-crash" tag. Also, rather than using the Attach method, you could listen to AppDomain.CurrentDomain.UnhandledException and TaskScheduler.UnobservedTaskException yourself and tag those exceptions based on if they cause an application crash.
We would only add this as a standard property on the details logged to Raygun.io if the provider is able to work it out itself.
Kind Regards
-Jason Fauchelle