Bug 59407 - ItemSelected and ItemTapped are blocked in a Listview when you add ContextActions
Summary: ItemSelected and ItemTapped are blocked in a Listview when you add ContextAct...
Status: RESOLVED DUPLICATE of bug 58833
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 2.4.0
Hardware: PC Windows
: Normal major
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-09-12 06:54 UTC by Jorge Garcia
Modified: 2017-09-12 16:55 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED DUPLICATE of bug 58833

Description Jorge Garcia 2017-09-12 06:54:54 UTC
When you add ContextActions in a Listview the ItemSelected and ItemTapped events are not fired.
This issue is only detected on Android devices (iOS and UWP are working fine).

The issue is detected with the combination of:
Xamarin.Forms v2.4.0.269-pre2
Xamarin.Android.Support Libraries v25.4.0.2

Reported by Jorge_CP
https://forums.xamarin.com/discussion/comment/296007#Comment_296007
Comment 1 Paul DiPietro [MSFT] 2017-09-12 16:55:02 UTC

*** This bug has been marked as a duplicate of bug 58833 ***