From my own research and trials trying to get the TestFlight SDK to work with MonoTouch, it seems that the error report does not really work. That's why:
Essentially, the TestFlight SDK inserts the obj-c global exception handler and then sends the exceptions, stack trace, etc. in TestFlight. Since the SDK is a NATIVE library, it will only receive its own obj-c exceptions. This means that none of your Mono exceptions will ever reach this global obj-c handler, because the handler runs at a lower level than the Mono runtime.
So, you can bind to your own test library TestFlight, you can call the TakeOff () method, etc. But in the end, all of this is pointless, because your single-level exceptions will never be caught. You can, of course, get obj-c exceptions when they happen, but that really will not help you with your Mono exceptions. Since all of your code is supposedly located in C # running at Mono runtime, do not expect your exceptions to fall into the TestFlight SDK handler.
If I'm wrong, someone, please correct me, but I do not believe that the TestFlight SDK will be useful until the MonoTouch library is written, which catches Mono exceptions and sends them to TestFlight.
source share