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
Developer Community or GitHub 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.
Got this stack trace on Xamarin Insights, sorry, not easily reproducible. I think you need to handle the case where uITableView.IndexPathForRowAtPoint() returns null in the ShouldReceiveTouch handler.
Object reference not set to an instance of an object
UIKit.UIApplication.Main(System.String args, IntPtr principal, IntPtr delegate)
UIKit.UIApplication.Main(System.String args, System.String principalClassName, System.String delegateClassName)
Should be easy enough to fix even though we have no idea what causes it, null check all the things in that method.
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d