This is Xamarin's bug tracking system. For product support, please use the support links listed in your Xamarin Account.
Bug 44886 - UWP Listview ItemSelected event triggered twice for each selection
Summary: UWP Listview ItemSelected event triggered twice for each selection
Status: VERIFIED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows (show other bugs)
Version: 2.3.2
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
: 45219 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-09-29 14:11 UTC by Taylor
Modified: 2016-11-03 12:05 UTC (History)
4 users (show)

See Also:
Tags: ac
Is this bug a regression?: Yes
Last known good build: 2.3.1.114


Attachments
Reproduction Project (246.70 KB, application/x-zip-compressed)
2016-09-29 14:16 UTC, Taylor
Details

Description Taylor 2016-09-29 14:11:43 UTC
The ItemSelected event is being triggered twice each time an item is selected on a listview.  This issue is only occuring on UWP with the latest version of Forms(2.3.2.127).

I have attached an example reproduction case.  When the app launched you will be presented with a very basic listview with 5 items.  Selecting one of those items will cause a dialog to appear telling you which item you selected.  Additionally, when run in debug mode the item you selected will be printed to the console.

When running on Android or iOS this dialog is only displayed once, and the selected item is printed to the console once.  On UWP this happens twice.
Comment 1 Taylor 2016-09-29 14:16:28 UTC
Created attachment 17803 [details]
Reproduction Project
Comment 2 Samantha Houts 2016-09-30 23:03:32 UTC
Should be fixed in 2.3.4-pre1. Thank you!
Comment 3 Samantha Houts 2016-10-14 18:52:36 UTC
*** Bug 45219 has been marked as a duplicate of this bug. ***
Comment 4 Parmendra Kumar 2016-11-03 12:05:55 UTC
I have checked this issue and observed that this issue has been fixed with Xamarin.Forms 2.3.3-pre3.

Hence closing this issue.

Note You need to log in before you can comment on or make changes to this bug.