Bug 36780 - [iOS] Multiple TapGestureRecognizers on an Object Are Not Fired
Summary: [iOS] Multiple TapGestureRecognizers on an Object Are Not Fired
Alias: None
Product: Forms
Classification: Xamarin
Component: iOS ()
Version: 2.3.3
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: E.Z. Hart [MSFT]
: 45014 45251 ()
Depends on:
Reported: 2015-12-09 17:53 UTC by Jimmy [MSFT]
Modified: 2017-06-21 11:16 UTC (History)
7 users (show)

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

repro solution (46.81 KB, application/zip)
2015-12-09 17:53 UTC, Jimmy [MSFT]

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:

Description Jimmy [MSFT] 2015-12-09 17:53:39 UTC
Created attachment 14207 [details]
repro solution

### Overview
On iOS, an object that has multiple TapGestureRecogizers will only fire one of them instead of all of them when activated.

### Steps to Reproduce
1. Run the attached iOS project
2. Press the Xamarin image repeatedly

### Expected Result
A green BoxView will toggle it’s visibility and a Label above the image will indicate the number of presses.

You can run the Android project instead to see the expected result.

### Actual Result
Only the BoxView will be toggled and the Label never appears since that TapGestureRecognizer does not seem to be fired.

### Environment Info
=== Xamarin Studio ===

Version 5.10.1 (build 6)
Installation UUID: 94ce5106-6a72-4691-b34e-cd5857b1db66
	Mono 4.2.1 (explicit/6dd2d0d)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 402010102

=== Xamarin.Profiler ===

Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Apple Developer Tools ===

Xcode 7.1.1 (9081)
Build 7B1005

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: eb4c1ef
Branch: master
Build date: 2015-12-01 02:12:30-0500

=== Xamarin.Android ===

Version: (Business Edition)
Android SDK: /Users/jimmygarrido/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.4   (API level 19)
		5.0   (API level 21)
		5.1   (API level 22)
		6.0   (API level 23)

SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.0.1
SDK Build Tools Version: 22.0.1

Java SDK: /usr
java version "1.7.0_79"
Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)

=== Xamarin Android Player ===

Version: 0.6.5
Location: /Applications/Xamarin Android Player.app

=== Xamarin.Mac ===

Version: (Business Edition)

=== Build Information ===

Release ID: 510010006
Git revision: 0b60eecdb531933734519c13257d16a780274aab
Build date: 2015-12-04 20:28:20-05
Xamarin addins: 9876fd7c9837977178411ec7375b4352c0a0d6af
Build lane: monodevelop-lion-cycle6-baseline

=== Operating System ===

Mac OS X 10.11.1
Darwin Jimmys-MacBook-Pro.local 15.0.0 Darwin Kernel Version 15.0.0
    Sat Sep 19 15:53:46 PDT 2015
    root:xnu-3247.10.11~1/RELEASE_X86_64 x86_64
Comment 2 Jimmy [MSFT] 2016-10-25 21:51:11 UTC
Still reproducible with Forms 2.3.3-pre3
Comment 3 E.Z. Hart [MSFT] 2017-06-02 23:21:02 UTC
PR: https://github.com/xamarin/Xamarin.Forms/pull/964
Comment 4 E.Z. Hart [MSFT] 2017-06-05 16:58:35 UTC
*** Bug 45014 has been marked as a duplicate of this bug. ***
Comment 5 E.Z. Hart [MSFT] 2017-06-05 17:27:36 UTC
*** Bug 45251 has been marked as a duplicate of this bug. ***
Comment 6 Rui Marinho 2017-06-21 11:16:18 UTC
Should be fixed on 2.3.6-pre1