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.
I have Xamarin Forms 188.8.131.5229 version and same version of Xamarin.Forms.Maps. There's an issue with Pins. I am having some problems with Pin.Clicked event. What happens is when I tap the pin, it just opens the balloon, but even is not fired. To fire the clicked event I must then tap the balloon of the pin. On iOS the behavior is a little bit different. When you tap on the pin, nothing happens, just the balloon opens. To trigger the event you'll need to tap on the pin again. I believe this is very strange behavior. Please fix this.
Hi Gagik, i have just tried to debug this issue, and when i tap the ballon it will fire the Clicked event, also if i tap the pin it also fires the Clicked event. This is the intended behaviour.
Xamarin Forms Team
Look the even is not fired when I click the pin first time, it's only fired when I click the pin or already appeared balloon for the second time. This shouldn't work like this, rather the clicked event should be fired when as soon as I click the pin. I believe this is how it should work.
And for Android it's even worse, the click event is only fired after you tap on the pin and tap on the balloon, and it doesn't work when you tap on pin, just the ballon.Have a look in this forum thread.
Can you add a repro?
@Gagik Kyurkchyan: Yes, please provide a small project that will demonstrate this issue to help us track down the cause. Thank you!
Xamarin Forms Team
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!
*** Bug 60129 has been marked as a duplicate of this bug. ***
Supposedly an issue per #60129 so I'm reopening this for now
Is there any progress on this bug?
As a reproduction has not been provided by anyone, this will be closed for now. Please open a new issue on GitHub with a reproduction project if you are still experiencing the behavior as of the latest stable release of Forms, as we use that for tracking now. Thanks.