Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Running a Xamarin app on the latest Xamarin.iOS (v7.0) on iPad mini, the app occasionally crashes with the following crash report from testflight (after the .dSYM was added):
# Binary Image Name Address Symbol
0 BlastOutAppUITouch 0x0002d712 testflight_backtrace
1 BlastOutAppUITouch 0x0002e360 TFSignalHandler
2 libsystem_platform.dylib 0x3b1e0062 _sigtramp
3 BlastOutAppUITouch 0x016b206c in threads.c on Line 1428
4 BlastOutAppUITouch 0x016b1a04 start_wrapper in threads.c on Line 608
5 BlastOutAppUITouch 0x016c8ea2 thread_start_routine in wthreads.c on Line 294
6 BlastOutAppUITouch 0x016d0f90 inner_start_thread in mono-threads-posix.c on Line 49
7 BlastOutAppUITouch 0x016e618a GC_start_routine in pthread_support.c on Line 1526
8 libsystem_pthread.dylib 0x3b1e4c1c _pthread_body
9 libsystem_pthread.dylib 0x3b1e4b8e _pthread_start
10 libsystem_pthread.dylib 0x3b1e2c8f thread_start
Seems to be too low level for my app-code to be at fault... Not sure what else I can provide to shed light on this issue.
This may be a NullRefenceException confusing TestFlight - this is explained (with a fix) here: http://stackoverflow.com/questions/14499334/how-to-prevent-ios-crash-reporters-from-crashing-monotouch-apps ?
If that's not the case please attach a complete crash report (it's also important to know what the other threads are doing).
We got this crash log from TestFlight, so that's probably it in this case!
Thanks for the incredibly rapid response! I shall expect virtual telepathy from Xamarin tech support in the near future ;)
I'm closing this then, please reopen if you can still reproduce after implementing the fix from comment #2.