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.
Unlike their iOS counterparts, these methods take no indication which element should be swiped and are therefore useless.
It's been almost a month, could you please at least comment? Without a way to point out what to swipe you might as well remove these methods.
The parameter less SwipeLeft() and SwipeRight() are generic actions.
For more specific operations you can use DragCoordinates (Single fromX, Single fromY, Single toX, Single toY). This can be combined with queries to calculate specific values for coordinates in the given situation, device, etc.
I know I can but it's unreliable. What does it mean that they are "generic actions"? Are they created this way at the OS level? Because if they are not, it can be done as it has been in the iOS version of UITests.
Moved this to Xamarin Test Cloud Ideas & Feature Requests Portal:
and created a matching internal feature request.