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.
When using Listview Context Actions in Android, if you long tap an item which brings up the action bar at the top and then click (single tap) on say another item in the list which opens that item the Contact Action bar at the top is not being removed and is still there which not only covers the new page's toolbar but also is still actionable.
I ran into the same problem today. It appears to arise from the Android platform's CellAdapter class. The private ActionMode's Finish() method is only ever called when one of the displayed menu items is tapped, or if another longclick is performed. It is not aware of navigation or other events.
Should be fixed in 1.4.0 final
Is that bug closed? I tried that feature on a listview on Android and iOs with Xamarin.Forms, works well with iOs, but get the same problem described here on Android. Using Xamarin Forms 184.108.40.20641 where the bug should have been resolved...
Just tried the "Xamarin.Forms 220.127.116.1147-pre2" and got the same bug.
I long tap on an item : context action bar for that item is shown
I long tap on another item of the list : context action bar of the previous long tapped item still shown. If i single tap on that item, nothing happens.
This is still a problem in 18.104.22.16892