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 for Bug 60295 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
== Overview: =================================
Suspected race-condition with PushModalAsync()
Multiple tapping on Buttons, TapGestureRecognizer (Image, Label, Grid and StackLayout etc...)
The ICommand process is invoked multiple times as much taps on button, TapGenstureRecognizer.
Disabling the control through IsEnabled of a button works, but this does not work when using TapGestureRecognizer Image, Label, MenuGrid as button etc.
== Steps to Reproduce: =======================
(Test on a tablet/phone if you are not able to reproduce within emulator)
1. Run attached sample (Xamarin Team only)
2. Click multiples times on the single button, in quick succession
3. Note multiple screens created
4. Code logic (bool isBusy) should have prevented multiple instances
== Actual Results: ===========================
Multiple instances are created, if the user clicks fast enough
== Expected Results: =========================
Only a single instance created
== Build Date & Platform: ====================