Bug 15590 - WebClient.UploadValuesTaskAsync returns "Error"
Summary: WebClient.UploadValuesTaskAsync returns "Error"
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.8.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2013-10-22 12:37 UTC by Miha Markic
Modified: 2017-06-30 04:27 UTC (History)
2 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 Miha Markic 2013-10-22 12:37:56 UTC
I am using WebClient.UploadValuesTaskAsync method to get a text from a HTTPS based Uri. It returns "Error" string (bytes for string of course).
The non-async counterpart WebClient.UploadValues works fine and the async MS version on Windows works as well.

I guess the problem might be caused from the fact that I am using untrusted certificates with 
ServicePointManager.ServerCertificateValidationCallback = delegate { return true; };
Comment 1 Jonathan Pryor 2013-11-01 17:00:42 UTC
Please provide a complete test case so that I can debug the issue.
Comment 2 Chris Hardy [MSFT] 2017-06-30 04:27:40 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!