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.
Put two buttons A and B on the same page and assign a PushAsync(PageA) respectively PushAsync(PageB) action on them. Press A and hold it, press B and hold it as well. Now let go of button A – PageA opens. If you now let go of B, PageB also opens.
Steps to reproduce with attached sample:
1. Open application
2. Deploy to device (easier to test)
3. Press one finger down on button A, hold down
4. Press finger down on Button B
5. Lift up Finger on A-> Navigates to Page A, keep Finger b down on screen
6. Lift finger B.
Actual result: B Button click is still registered and navigates to Page B despite the context has changed.
See project sample here:
Seems to be happening on Android (tried an S5) but not iOS (tried an iPhone 6).
Thank you for your report. At this time there are no plans to implement any changes around this issue. This is pretty much how the underlying toolkits operate.
Xamarin Forms Team