BackgroundDownloadProgress.TotalBytesToReceive is always zero in Build 1903
See original GitHub issueDescription
When using the BackgroundTransfer API in Windows 10 Build 1903, BackgroundDownloadProgress.TotalBytesToReceive
is always zero.
This means you cannot determine the progress of a download operation.
Steps to Reproduce
- Download and run the BackgroundTransfer sample.
- Observe the log output “Transferred bytes: x of 0”
Expected Behavior
TotalBytesToReceive
should not be zero.
Actual Behavior
TotalBytesToReceive
is always zero on Windows 10 Build 1903.
Basic Information
- Version with issue:
- Last known good version: Windows 10 Build 1809
Reported on the Windows Developer Feedback forum: https://wpdev.uservoice.com/forums/110705-universal-windows-platform/suggestions/38253688-backgrounddownloadprogress-totalbytestoreceive-is
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:5 (2 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Good news! We have a fix, and it will be part of the next windows. If you’re on an insider build, you should already have the fix as of mid-September.
Peter Smith PM for the Network Developer Experience team
From: Thomas Pentenrieder notifications@github.com Sent: Monday, November 18, 2019 2:50 AM To: microsoft/Windows-universal-samples Windows-universal-samples@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [microsoft/Windows-universal-samples] BackgroundDownloadProgress.TotalBytesToReceive is always zero in Build 1903 (#1125)
Since the UserVoice is no longer being used and I can’t see any issue related to this in https://github.com/MicrosoftDocs/windows-uwp/issueshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwindows-uwp%2Fissues&data=02|01|pesmith%40microsoft.com|2b9392e864ef441ec5e108d76c150871|72f988bf86f141af91ab2d7cd011db47|1|0|637096709901282016&sdata=D6iA4b9vK5QS2y%2Bvi%2FZiLsy8l9%2B59GaI3oVg%2FdBw5Kc%3D&reserved=0 I was wondering if this has been addressed? I’m still seeing TotalBytesToReceive being 0 despite the content-length header being set on the server (double-checked using Postman). Should I be opening a new issue in the windows-uwp repo?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FWindows-universal-samples%2Fissues%2F1125%3Femail_source%3Dnotifications%26email_token%3DAG6ITNYAVBWX34MW5QDRX2DQUJXMZA5CNFSM4IHSJJG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEKAVRQ%23issuecomment-554961606&data=02|01|pesmith%40microsoft.com|2b9392e864ef441ec5e108d76c150871|72f988bf86f141af91ab2d7cd011db47|1|0|637096709901292010&sdata=Qum3F8gLSU0r%2BPjLBmh83HsQOpUqiQkvj%2B%2FYDuGahuM%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAG6ITN643VFTYZAWWJOZUO3QUJXMZANCNFSM4IHSJJGQ&data=02|01|pesmith%40microsoft.com|2b9392e864ef441ec5e108d76c150871|72f988bf86f141af91ab2d7cd011db47|1|0|637096709901292010&sdata=LRYnITZyNrW55LeOY9lBvTSjkoiZYxinKoMmvPREvmU%3D&reserved=0.
(FYI, https://github.com/MicrosoftDocs/windows-uwp/issues is for reporting issues with the docs, not issues with the platform.)