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.
I have a ListView in Xamarin.Forms that is displaying ImageCells. The app crashes at the Main.cs file and says “Only a single Cancel() call is supported at a time." The error occurs when scrolling quickly up and down the ListView.
Created attachment 9138 [details]
I have checked this issue and unable to reproduce it with the help of bug description.
I tried following steps to reproduce it.
1. Create a Xamarin forms application.
2. Add a class President.cs
3.Implement code in president.cs(Implemented code written in attached file).
4.Add class ListViewDemoPage.cs
5.Implement code in ListViewDemoPage.cs.
6.Call ListViewDemoPage.cs in App.cs
7.Set iOS as startup project.
8.Run the application.
9.Observed that Listview scrolling working fine.
10.Set android as startup project.
11.Run the application.
12.Observed that application working fine and does not crash and also observed that image on scrolling getting late on loading only in case of android.
Please let me know if i missed anything to reproduce this issue?
Could you please provide us sample app,Environment info and steps to reproduce this issue ?
Screencast : http://www.screencast.com/t/PJV7LFAyTb
Ide logs :https://gist.github.com/Arpit360/98d828e35387d2cfce69
Xamarin.forms version : 1.2.3
=== Xamarin Studio ===
Version 5.5.4 (build 15)
Installation UUID: 3d25a767-a003-4a7d-9f5e-e57987cf6cf0
Mono 3.10.0 ((detached/92c4884)
GTK+ 2.24.23 (Raleigh theme)
Package version: 310000031
=== Apple Developer Tools ===
Xcode 6.1 (6602)
=== Xamarin.Mac ===
Version: 18.104.22.168 (Enterprise Edition)
=== Xamarin.Android ===
Version: 22.214.171.124 (Enterprise Edition)
Android SDK: /Users/mac360_xamarin/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
2.1 (API level 7)
2.2 (API level 8)
2.3 (API level 10)
3.1 (API level 12)
4.0.3 (API level 15)
4.4 (API level 19)
5.0 (API level 21)
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)
=== Xamarin.iOS ===
Version: 126.96.36.199 (Enterprise Edition)
Build date: 2014-11-16 21:03:22-0500
=== Build Information ===
Release ID: 505040015
Git revision: f93940a35458a18052f1a25e106e62ca970d9c40
Build date: 2014-11-19 15:32:41-05
Xamarin addins: dc23cbd91a3a0e1d326328e1229e86c942a49ec8
=== Operating System ===
Mac OS X 10.10.0
Darwin mac360-xamarins-Mac-mini.local 14.0.0 Darwin Kernel Version 14.0.0
Fri Sep 19 00:26:44 PDT 2014
Thank you for taking the time to submit this report. After reviewing the description of this bug, we no longer believe it affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d
Xamarin Forms Team