Bug 29250 - TapGestureRecognizer.Tapped does not fire when added to a Map
Summary: TapGestureRecognizer.Tapped does not fire when added to a Map
Status: RESOLVED NORESPONSE
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.4.1
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-04-20 13:50 UTC by Matthew Regul
Modified: 2017-01-04 17:50 UTC (History)
7 users (show)

Tags: all functional maps
Is this bug a regression?: ---
Last known good build:


Attachments
Test case (188.55 KB, application/zip)
2015-04-20 13:50 UTC, Matthew Regul
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 NORESPONSE

Description Matthew Regul 2015-04-20 13:50:55 UTC
Created attachment 10826 [details]
Test case

**Overview:**

   When a TapGestureRecognizer is added to a Xamarin Forms Map, no tap event is fired.

**Steps to Reproduce:**

   1. Run attached sample on iOS
   2. Touch the map

**Actual Results:**

   TapGestureRecognizer.Tapped event is not fired

**Expected Results:**

   TapGestureRecognizer.Tapped event fires

**Build Date & Platform:**

   Xamarin.Forms 1.4.1
Comment 1 asimk 2015-04-24 07:50:30 UTC
I have checked this issue with the help of sample app attached in Bug description and able to reproduce this issue. I observed that when I tap on Map, Tapped event is not fired.

I have checked this issue with Simulator and Device both.

Screencast: http://www.screencast.com/t/8TVYQ8ensUdf
Ide Log: https://gist.github.com/saurabh360/81bd18e1e7df047f5b90
iOS Designer Log: https://gist.github.com/saurabh360/8c53880e0007f3fd6044

Environment Info:
=== Xamarin Studio ===

Version 5.9 (build 436)
Installation UUID: d6f15b80-470e-4e50-9aba-38a45c556680
Runtime:
 Mono 4.0.0 ((detached/fd35b80)
 GTK+ 2.24.23 (Raleigh theme)

 Package version: 400000145

=== Apple Developer Tools ===

Xcode 6.3 (7569)
Build 6D570

=== Xamarin.iOS ===

Version: 8.10.0.266 (Business Edition)
Hash: c8648f0
Branch: master
Build date: 2015-04-21 12:22:24-0400

=== Xamarin.Android ===

Version: 5.1.0.115 (Business Edition)
Android SDK: /Users/360logica/Desktop/Anddk/android-sdk-macosx
 Supported Android versions:
  2.3    (API level 10)
  4.0.3  (API level 15)
  4.1    (API level 16)
  4.2    (API level 17)
  4.3    (API level 18)
  4.4    (API level 19)
  4.4.87 (API level 20)
  5.0    (API level 21)
Java SDK: /usr
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)

=== Xamarin Android Player ===

Version: Unknown version
Location: /Applications/Xamarin Android Player.app

=== Xamarin.Mac ===

Version: 2.0.0.266 (Business Edition)

=== Build Information ===

Release ID: 509000436
Git revision: 7e8ba4cbccf7b188ce5e80a90fdc4acdedb5a83f
Build date: 2015-04-23 13:19:57-04
Xamarin addins: 21fd95f743742c5237e22023996c2800ce3f8db3

=== Operating System ===

Mac OS X 10.10.0
Darwin 360Logicas-MacBook-Pro.local 14.0.0 Darwin Kernel Version 14.0.0
    Fri Sep 19 00:26:44 PDT 2014
    root:xnu-2782.1.97~2/RELEASE_X86_64 x86_64
Comment 2 Chris King 2015-05-28 16:59:04 UTC
We'd be happy to help you resolve this issue. Please help us by attaching a reduced reproduction to the bug by starting with a clean Xamarin.Forms project and adding just the code necessary to demonstrate the issue. If you'd do this for us we would very much appreciate it. Please do not include any unnecessary nuget packages. 

Warm regards,
Xamarin Forms Team
Comment 3 Rui Marinho 2017-01-04 17:50:39 UTC
Thank you for your bug report. As we have not received the information requested, we cannot properly triage your bug and are marking it resolved.

Warm regards, 
Xamarin Forms Team