Bug 27782 - Hard crash, as soon as a item in a ListView is selected and then changed (1.4-Pre-2)
Summary: Hard crash, as soon as a item in a ListView is selected and then changed (1.4...
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.4.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-03-09 13:01 UTC by Fredy Wenger
Modified: 2015-05-06 16:18 UTC (History)
4 users (show)

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


Attachments
Details to bug (617.55 KB, application/pdf)
2015-03-09 13:01 UTC, Fredy Wenger
Details


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 FIXED

Description Fredy Wenger 2015-03-09 13:01:06 UTC
Created attachment 10221 [details]
Details to bug

XF Android: Hard crash, as soon as a item in a ListView is selected and then changed (while it works on iOS).
Detail-description and download-link to project see attachment.
=> This makes the whole app unusable.
Comment 1 Jason Smith [MSFT] 2015-03-09 18:06:31 UTC
Should be fixed in 1.4.1-pre1
Comment 2 Mariella de Jong 2015-05-06 16:18:34 UTC
I just installed Xamarin.Forms 1.4.2 and the issue still exists in that build.