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 for Bug 60769 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 25762 [details]
Example with bug
Listview item selected event is not fired on iOS if ListView container has TapGestureRecognizer bound to it.
1) create a container view (Stack, Grid, Frame, ContentViev ...)
2) add TapGestureRecognizer to the container view
3) add ListView inside the container and populate it with items
4) subscribe to ListView.ItemSelected event
5) Run app and click any item in the ListView
Item in the ListView is selected, ItemSelected event is fired
Item in the ListView is not selected, ItemSelected event is not fired
How is this behaving on Android? Sounds like the parent view is trapping gestures instead of gestures bubbling up from child to parent. Issues like this were common a while back, and unfortunately different platforms don't always seem to be acting similarly.
On iOS, I think this is the default behavior. More discussion here: https://stackoverflow.com/questions/5222998/uigesturerecognizer-blocks-subview-for-handling-touch-events
Still though, the lack of consistency across multiple platforms is not good, IMO.
Android is fine, issue appears right after Ive update Xamarin Forms 2.3->2.4
Now I downgraded to 2.3 and it is fine. So it is definitely not default behavior it is new bug in 2.4. Also checked with 2.5 issue still present
Any updates guys
We will provide updates as the bug is being investigated and worked on.
Good, any approximate date?
Not at this time.
How is it going guys, have you fixed this bug already?