Bug 60893 - [Android] TapGestureRecognizer do not respond consistently to taps
Summary: [Android] TapGestureRecognizer do not respond consistently to taps
Status: RESOLVED ANSWERED
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 2.5.0
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-11-28 14:57 UTC by rr
Modified: 2018-02-12 18:20 UTC (History)
4 users (show)

Tags: Android, TapGestureRecognizer, ac
Is this bug a regression?: ---
Last known good build:


Attachments
repod project (188.11 KB, application/x-rar)
2017-11-28 14:57 UTC, rr
Details


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 ANSWERED

Description rr 2017-11-28 14:57:05 UTC
Created attachment 25850 [details]
repod project

**Overview:**

On Android the TapGestureRegenisor do not consistently fire the tapped event.
This is a problem on a Samsung Galaxy S6 and a Samsung Galaxy 7 both with android 7.0 (api 24).
However this problem is not present on a Nexus 5X with with android 8.0.0 (api 26)


**Steps to Reproduce:**

   1. Run the attached sample on a Galaxy S6 w. 7.0(lvl24)
   2. first tap the top (red) lable then the buttom (black)
   3. repeats this about 10 times and you will se the counters has missed some taps. in my case the buttom more than the top.

**Actual Results:**
  
  The tap event will not consistently fire. 
  in the debug output you can see:

exampel:
11-28 15:38:44.918 D/ViewRootImpl@2553e9e[MainActivity]( 1164): ViewPostImeInputStage processPointer 0
11-28 15:38:44.983 D/ViewRootImpl@2553e9e[MainActivity]( 1164): ViewPostImeInputStage processPointer 1
[0:] _titleBar1 tap detected
11-28 15:38:45.699 D/ViewRootImpl@2553e9e[MainActivity]( 1164): ViewPostImeInputStage processPointer 0
11-28 15:38:45.766 D/ViewRootImpl@2553e9e[MainActivity]( 1164): ViewPostImeInputStage processPointer 1
11-28 15:38:49.336 D/ViewRootImpl@2553e9e[MainActivity]( 1164): ViewPostImeInputStage processPointer 0
11-28 15:38:49.402 D/ViewRootImpl@2553e9e[MainActivity]( 1164): ViewPostImeInputStage processPointer 1
[0:] _titleBar1 tap detected
11-28 15:38:54.201 D/ViewRootImpl@2553e9e[MainActivity]( 1164): ViewPostImeInputStage processPointer 0
11-28 15:38:54.278 D/ViewRootImpl@2553e9e[MainActivity]( 1164): ViewPostImeInputStage processPointer 1
[0:] _titleBar2 tap detected
11-28 15:38:55.380 D/ViewRootImpl@2553e9e[MainActivity]( 1164): ViewPostImeInputStage processPointer 0
11-28 15:38:55.434 D/ViewRootImpl@2553e9e[MainActivity]( 1164): ViewPostImeInputStage processPointer 1
[0:] _titleBar1 tap detected

in this case the phone missed a tap to the buttom black bar.

the ViewPostImeInputStage processPointer is not observed on the Nexus5X 8.0 test.

**Expected Results:**

   The TapGestureRecognizer shuld fire the event when tapped.

**Build Date & Platform:**

   28nov2017
   VisualStudio17pro
   Xamarin.Forms 2.5.0.91635

**Additional Information:**

  the top red bar overlayed by a transparrent boxView and adding a TapGE to the box view.
  the buttom black bar is a grid that has been added a TapGE.

  this might be related to:
https://bugzilla.xamarin.com/show_bug.cgi?id=25943
or
https://bugzilla.xamarin.com/show_bug.cgi?id=59961
Comment 1 rr 2017-11-28 15:25:11 UTC
Now also observed on a Lenovo A Plus (android 5.1 API 22)

debug output, this time it missed the buttom tap two time in a row.

11-28 15:15:04.485 D/Surface ( 6847): Surface::setBuffersDimensions(this=0xb45b0c00,w=480,h=854)
11-28 15:15:04.588 D/FeatureProxyBase( 6847): FeatureProxyBase class constructor
11-28 15:15:04.588 D/FeatureProxyBase( 6847): getService(), serviceName = multiwindow_service_v1
[0:] _titleBar1 tap detected
11-28 15:15:04.666 D/Surface ( 6847): Surface::setBuffersDimensions(this=0xb45b0c00,w=480,h=854)
11-28 15:15:04.752 D/FeatureProxyBase( 6847): FeatureProxyBase class constructor
11-28 15:15:04.752 D/FeatureProxyBase( 6847): getService(), serviceName = multiwindow_service_v1
11-28 15:15:04.916 D/FeatureProxyBase( 6847): FeatureProxyBase class constructor
11-28 15:15:04.916 D/FeatureProxyBase( 6847): getService(), serviceName = multiwindow_service_v1
[0:] _titleBar1 tap detected
11-28 15:15:05.005 D/Surface ( 6847): Surface::setBuffersDimensions(this=0xb45b0c00,w=480,h=854)
11-28 15:15:05.080 D/FeatureProxyBase( 6847): FeatureProxyBase class constructor
11-28 15:15:05.080 D/FeatureProxyBase( 6847): getService(), serviceName = multiwindow_service_v1
11-28 15:15:05.258 D/FeatureProxyBase( 6847): FeatureProxyBase class constructor
11-28 15:15:05.258 D/FeatureProxyBase( 6847): getService(), serviceName = multiwindow_service_v1
[0:] _titleBar1 tap detected
11-28 15:15:05.360 D/Surface ( 6847): Surface::setBuffersDimensions(this=0xb45b0c00,w=480,h=854)
11-28 15:15:05.518 D/FeatureProxyBase( 6847): FeatureProxyBase class constructor
11-28 15:15:05.518 D/FeatureProxyBase( 6847): getService(), serviceName = multiwindow_service_v1
[0:] _titleBar2 tap detected
Comment 2 Paul DiPietro [MSFT] 2017-12-01 17:39:02 UTC
It seems like I can reproduce this on an S8 (running 7.0) but it's easier to make it occur when alternating between the two more rapidly.
Comment 3 rr 2017-12-14 13:07:37 UTC
Any updates on this? the users are getting very annoyed with this :)
Comment 4 Samantha Houts [MSFT] 2018-02-12 18:20:55 UTC
This issue has been migrated to https://github.com/xamarin/Xamarin.Forms/issues/1374. Please follow that issue for updates. Thanks!