Bug 11183 - Call to System.Net.Http.HttpClient.GetAsync() broken pipe
Summary: Call to System.Net.Http.HttpClient.GetAsync() broken pipe
Alias: None
Product: Android
Classification: Xamarin
Component: Pre-release ()
Version: 4.7.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2013-03-15 10:38 UTC by Clement
Modified: 2013-03-15 11:55 UTC (History)
1 user (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 Clement 2013-03-15 10:38:11 UTC
I'm using an API that was at first develop for Windows 8, it builds just fine however calling the function GetAsync() gets the application to freeze.

The line:
response = await httpClient.GetAsync(targetUri + content); (both param being correct strings)

No Exception is thrown.

Android Log reports this:

03-15 14:32:31.591 D/ExchangeService(  604): Received deviceId from Email app: null
03-15 14:32:31.591 D/ExchangeService(  604): !!! deviceId unknown; stopping self and retrying
03-15 14:32:31.871 W/SocketClient(   34): write error (Broken pipe)
03-15 14:32:31.871 W/DnsProxyListener(   34): Error writing DNS result to client

This was tested using an emulator running under API 17.
Comment 1 Jonathan Pryor 2013-03-15 11:55:21 UTC
The "broken pipe" message is not coming from your app. Pay careful attention to the pid in the messages:

> W/SocketClient(   34): write error (Broken pipe)
> W/DnsProxyListener(   34): Error writing DNS result to client

I highly doubt that your program is pid 34; to confirm, run:

    $ adb shell ps | grep 34

Then see if the printed process name matches your app's package name.