Bug 60208 - TapGestureRecognizer doesn't respond consistently to taps
Summary: TapGestureRecognizer doesn't respond consistently to taps
Status: RESOLVED DUPLICATE of bug 59863
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-10-16 15:09 UTC by Ed Owens
Modified: 2017-10-16 19:10 UTC (History)
5 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 59863

Description Ed Owens 2017-10-16 15:09:51 UTC
The enclosed solution is a highly streamlined version of my app.  It currently takes a indeterminate number of taps on the screen to register in the TapGestureRecognizer.  Interestingly, an earlier version of the program worked fine.  Since then I have updated all of my tools using NuGet update, including updates to Xamarin.  At this point, this anomaly occurred.  If the shapes are larger (1.00) there is a higher probability of tapping but it is still not every time.  (The original app has three shape sizes, 0.33, 0.66 and 1.00)  NOTE: the colored backgrounds are there simply because your response to a previous similar problem suggested it.

The OUTPUT window gives this: (It is interesting that the first tap hits right off, but not later taps).
...
10-16 22:45:06.803 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:06.896 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:07.231 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:07.323 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:07.735 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:07.811 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:07.822 D/Mono    (32019): Unloading image System.Diagnostics.Debug.dll [0xc9a71a00].
10-16 22:45:07.822 D/Mono    (32019): Image addref System.Diagnostics.Debug[0xcc9c8f60] -> System.Diagnostics.Debug.dll[0xcd058700]: 5
10-16 22:45:07.822 D/Mono    (32019): Config attempting to parse: 'System.Diagnostics.Debug.dll.config'.
10-16 22:45:07.822 D/Mono    (32019): Config attempting to parse: '/usr/local/etc/mono/assemblies/System.Diagnostics.Debug/System.Diagnostics.Debug.config'.
10-16 22:45:07.822 D/Mono    (32019): Assembly Ref addref TapTester[0xe5f138e0] -> System.Diagnostics.Debug[0xcd277040]: 3
10-16 22:45:07.822 D/Mono    (32019): Assembly Ref addref System.Diagnostics.Debug[0xcd277040] -> System[0xcd275ae0]: 10
[0:] Tap In:0
10-16 22:45:09.111 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:09.210 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:09.719 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:09.804 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:10.365 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:10.441 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:11.020 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:11.105 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:12.250 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:12.351 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:12.771 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:12.862 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:13.267 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:13.344 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
[0:] Tap In:1
10-16 22:45:14.761 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:14.830 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:15.297 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:15.374 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:15.746 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:15.814 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:16.204 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
[0:] Tap In:2
10-16 22:45:16.271 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:17.817 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:17.884 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:18.393 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:18.469 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
[0:] Tap In:3
10-16 22:45:19.604 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:19.679 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:20.219 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
10-16 22:45:20.302 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 1
10-16 22:45:20.747 D/ViewRootImpl@8e4b72e[MainActivity](32019): ViewPostImeInputStage processPointer 0
...
Comment 1 Jon Douglas [MSFT] 2017-10-16 15:20:25 UTC
Moving to Forms for visibility
Comment 2 Ed Owens 2017-10-16 15:24:15 UTC
Attachment didn't load, too large.  Find it HERE:
https://1drv.ms/u/s!Ak530OCobHh6gV-soeTbOk2EStYB
Comment 3 Paul DiPietro [MSFT] 2017-10-16 19:10:31 UTC
https://github.com/xamarin/Xamarin.Forms/pull/1188

Marking as a dupe of one of the related reports, as there have been at least three.

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