Provide more context for async errors in C# providers

I'm not sure if this should be classified as a bug report or a feature request, so I figured I'd just start here. I'm hitting some scenarios in my apps where exceptions are being thrown (and caught, and subsequently sent to Raygun) from async methods. The stacktrace visible in the dashboard just shows one stacktrace which doesn't provide any valuable information. I see from the code that it is just creating a StackTrace object from the exception and using that, so this makes sense.

That said, if you ToString() the exception in code there's a few more stacktraces available that provide much better context into where the error came from. Mono's implementation is a good example of where this comes from. Would it be possible to include something like this in the Raygun report, or, at the very least, also provide the ToString() output? I'm currently doing this from a Xamarin.iOS app, but judging from the code it looks like it would apply across the board.

Thanks for the quick fix! What's the timeline on getting the component updated? That would be ideal, but I'm happy to just grab it from GitHub if that's going to take some time.

No problem, will do.

Is there a reason the change was only made for iOS? This situation is going to happen in all of the C# platforms.

My initial tests of the new provider are looking good, thanks! I will report back if I notice any problems as I use it more.

It looks like this change never made it into the Xamarin.Android build for Raygun. Would it be possible to add it there as well? I'm currently in the same situation on Android that I was when I reported this about iOS - getting error reports that have no useful information in them.

Thanks!

Thanks for the quick turnaround on this, it definitely improves things. One thing I noticed is that the frames reported in the new version start with "undefined.undefined", which is not something I've seen in the iOS version. For example:

OloApiException: Please try this operation again or restart your application.
OloApiClient.Network.ResponseExtensions+<Process>c__async2`1[OloApiClient.Entities.OrderStatus].MoveNext():0
undefined.undefined in --- End of stack trace from previous location where exception was thrown ---:0
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw():0
System.Runtime.CompilerServices.TaskAwaiter`1[OloApiClient.Entities.OrderStatus].GetResult():0
AppCore.ViewModels.Checkout.PlaceOrderViewModelBase+<placeOrder>c__async2A.MoveNext():0
undefined.undefined in --- End of stack trace from previous location where exception was thrown ---:0
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw():0
System.Runtime.CompilerServices.TaskAwaiter.GetResult():0
AppCore.ViewModels.Base.ViewModelBase+<SafeOperation>c__async0.MoveNext():0