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.
Using the default System.Net.Http.HttpClientHandleron Android to connect via SSL can result in no body being returned even though the connection has been successfully established. This may also relate to which TLS versions the server supports, in our case it uses 1.0 and 1.2 but not 1.1.
This issue only occurs on Android with iOS and Windows working correctly with the same code.
This issue can be fixed by using Xamarin.Android.Net.AndroidClientHandler() instead with everything else being identical.
Possibly related to/was found with https://bugzilla.xamarin.com/show_bug.cgi?id=50587
System.Net.Http.HttpClientHandler doesn't support TLS 1.2 in the current releases of XA. You need to either use AndroidClientHandler as you mention or wait for XA release that supports TLS 1.2 (should be out soon)