Bug 44786 - Xamarin Forms iOS 10 bug in listview context menu item (Value cannot be null. Parameter name: gestureRecognizer)
Summary: Xamarin Forms iOS 10 bug in listview context menu item (Value cannot be null....
Status: RESOLVED DUPLICATE of bug 44338
Alias: None
Product: Forms
Classification: Xamarin
Component: iOS ()
Version: 2.3.2
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-09-27 15:34 UTC by Fábio Alexandre
Modified: 2016-10-10 16:02 UTC (History)
7 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED DUPLICATE of bug 44338

Description Fábio Alexandre 2016-09-27 15:34:43 UTC
The problem occurs in ios sdk 10. The scenario is you swipe to pull the menu item and when you tap out of that item (you wanna cancel) it supposed to close the menu item in the listview. This was working in iOS 9. In iOS 10 when you tap outside the menu item you get an error:

System.ArgumentNullException: Value cannot be null. Parameter name: gestureRecognizer.
Comment 1 Salman Gadit 2016-09-28 05:15:28 UTC
+1 I see this issue in iOS 10 as well. This seems to be a simple enough fix. I have only tested on iOS 10 so far.
Comment 2 Stefano Bono 2016-09-30 07:55:43 UTC
+1 I have this BUG on iOS 10. On iOS 9 this works perfectly.
Comment 3 Stefano Bono 2016-09-30 08:27:57 UTC
I Think that this BUG is also reported here: Bug 44338
Comment 4 E.Z. Hart [MSFT] 2016-10-10 16:02:19 UTC

*** This bug has been marked as a duplicate of bug 44338 ***