Xamarin for Raygun not reporting all crashes

Hello

Thanks for pointing this out and sending the crash report examples.

As far as we can tell, The Xamarin framework has trouble detecting these kinds of exceptions. I have read that putting a try/catch block around the Main code can help catch these. Although this is not a recommended coding practice, it may be worth trying it out to see if these exceptions can be picked up.

Does your application have a native objective-c part? Crashes occurring within the objective-c code may be what's causing these un-catchable exceptions. If you could send us some more information related to the actions taken to cause these random exceptions, that would help us to reproduce this and see if anything can be done to improve this scenario.

We have plans for early this year to use our new native objective-c Raygun provider at the core of the Xamarin provider which should also improve the ability to catch these exceptions.

-Jason Fauchelle

A little while ago we released a new beta version of the Raygun Xamarin iOS provider which is now able to detect and report native exceptions as described in this forum thread. For anyone interested in this, you can read more information about this here: https://raygun.io/blog/2014/10/report-native-ios-errors-new-beta-xamarin-provider/

To anyone who stumbles upon this thread,

Raygun4Net for Xamarin.iOS now supports reporting native errors. This functionality is available in both the classic and Unified API versions. This is available from NuGet and Xamarin Component Store - both built on the stable channel of Xamarin.iOS.

More information, and instructions to enable this is available here: https://raygun.io/blog/2015/01/raygun-for-xamarin-ios-supports-unified-api-and-native-error-reporting/

-Jason Fauchelle