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.
It is possible to swipe multiple ListView Cells to see the context actions.
Steps to reproduce:
1. ListView with ContextActions
2. Swipe multiple Cells at the same time
3. tap the context action button
4. Action is applied to other cells then the selected one
- It shouldn't be possible to swipe more than one cell at a time
I can somewhat confirm.
On iOS10 devices, when trying to swipe the second cell, it crashes and raises an System.ArgumentNullException with the message:
Value cannot be null.
Parameter name: gestureRecognizer
It originates from UIKit.UIView.RemoveGestureRecognizer, from what I can tell.
Using Forms 188.8.131.52 it seems to work on iOS 9 devices.
@Xet: you were supposed to open a new bug for the crash. It's important. couldn't find one... did you do it?
No I did not, since I figured that the issues reported in the bug is directly related to the crash.
I confirm the behaviour described by @Xet on iOS 10 devices.
Reproduced Xet. Opened "ContextActions List Gallery" on iOS > Open context actions for one row > Try open context actions for another. Observed exception.
The second bug you all are describing should soon be fixed. See https://github.com/xamarin/Xamarin.Forms/pull/442. I'm wondering if the first comment indicates another bug.
Should be fixed in 2.3.4-pre2