Bug 19690 - HttpClient failing to load in release mode
Summary: HttpClient failing to load in release mode
Status: RESOLVED INVALID
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.12.4
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2014-05-12 14:39 UTC by Peter Collins
Modified: 2014-05-12 15:42 UTC (History)
3 users (show)

Tags:
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:
Status:
RESOLVED INVALID

Description Peter Collins 2014-05-12 14:39:22 UTC
Filing a new issue from a recent comment in Bug 17397:
"We are observing the same symptoms- httpclient failing to load only in release
mode calling HTTPS service. What is worse, in our setup it is silently failing
with no logcat output of exceptions. 
We are using Xamarin.Android 4.12.4.10"

Could you please provide a code snippet or project that reproduces the failure you're seeing here? We have made some changes to our web/http stack in 4.12.4 and would very much like to help get to the bottom of this issue!
Comment 1 v7d 2014-05-12 15:30:09 UTC
In the attempt to re-create the issue in a separate project we have found the root cause to be internal issue.