Bug 2482 - DownloadProgressChanged's BytesReceived does not increment
Summary: DownloadProgressChanged's BytesReceived does not increment
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 5.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Sebastien Pouliot
Depends on:
Reported: 2011-12-13 13:01 UTC by Chris Hardy [MSFT]
Modified: 2011-12-19 14:17 UTC (History)
4 users (show)

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:

Description Chris Hardy [MSFT] 2011-12-13 13:01:27 UTC
The BytesReceived from using DownloadProgressChanged with a DownloadDataAsync method only shows the amount of bytes downloaded at each change and does not increment as it does when using DownloadFileAsync.

Here's a MonoTouch reproduction of the problem: https://gist.github.com/d4c87703d3453f086aa2 (Button text updates when pressed with BytesReceived).
Comment 1 Sebastien Pouliot 2011-12-19 13:20:17 UTC
Look like a typo and the warnings were not seen and later commented [1]. Will correct and test it.

[1] https://github.com/xamarin/mono/commit/bdd9de656eb42d813791571948e40c21c0c5f095
Comment 2 Sebastien Pouliot 2011-12-19 14:17:32 UTC
Fixed in mono's master, mono-2-10 and in mobile-master
Next 5.1.x beta will have the fix.