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.
Created attachment 25414 [details]
This might be related to #59863 and #59961, but I wanted to post a repro to show a different perspective in the matter comparing Android button clicks to gesture recognizers. If you run the repro, you will see a Grid with a Label and a Button below the grid. Tap as many times as you like on each (50+) to notice that Button clicks are instantaneous whereas the gesture recognizer sometimes does not fire. Why is that? This is a critical issue in my opinion as many of us use gestures widely.
Tested this on 2.5.0-pre2 with S6.
Please make sure to test this with taps on the Label vs taps on the Grid. It seems that sometimes the label traps taps whereas other times tapping on the Grid (close to the edges) does not fire taps.
The button seems a lot more sensitive to finger touches.
Another way to test this is by trying to register taps when the phone is rotated in one direction (for example tilt it to the left 45 degrees) so that finger touches are not direct. Here, the gesture recognizer performs very poorly compared to the button.
I can confirm this issue. Our application works ok on XF 2.3.4
After updating to XF 2.4 we got a lot of missed taps from TapGestureRecognizer.
Just tested the fix for 59863 against this repro and it worked.
*** This bug has been marked as a duplicate of bug 59863 ***