Bug 20441 - Xamarin 3.0 - New Crash - IO exception during Write. ---> System.IO.IOException: BeginWrite failure
Summary: Xamarin 3.0 - New Crash - IO exception during Write. ---> System.IO.IOExcepti...
Status: RESOLVED INVALID
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 4.14.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Marek Habersack
URL:
Depends on:
Blocks:
 
Reported: 2014-06-06 15:24 UTC by mlpstingray
Modified: 2017-06-27 02:07 UTC (History)
5 users (show)

Tags: bb
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 mlpstingray 2014-06-06 15:24:41 UTC
There is a new bug in Xamarin Android 4.14.4 that occurs when you make an HTTPS request on a server which doesn't hold that certificate. 

Before, the request was failing normally (testted on Xamarin Android 4.14.3) but now it prints the following callstack :

>System.IO.IOException: IO exception during Write.
>06-06 14:56:52.799 E/mono    (11666): 
>06-06 14:56:52.799 E/mono    (11666): Unhandled Exception:
>06-06 14:56:52.799 E/mono    (11666): System.IO.IOException: IO exception during Write. ---> System.IO.IOException: BeginWrite failure
>06-06 14:56:52.799 E/mono    (11666):   at System.Net.Sockets.NetworkStream.BeginWrite (System.Byte[] buffer, Int32 offset, Int32 size, System.AsyncCallback callback, System.Object state) [0x00000] in <filename unknown>:0 
>06-06 14:56:52.799 E/mono    (11666):   at Mono.Security.Protocol.Tls.SslStreamBase.InternalBeginWrite (Mono.Security.Protocol.Tls.InternalAsyncResult asyncResult) [0x00000] in <filename unknown>:0 
>06-06 14:56:52.799 E/mono    (11666):   --- End of inner exception stack trace ---
>06-06 14:56:52.799 E/mono    (11666):   at Mono.Security.Protocol.Tls.SslStreamBase.InternalBeginWrite (Mono.Security.Protocol.Tls.InternalAsyncResult asyncResult) [0x00000] in <filename unknown>:0 
>06-06 14:56:52.799 E/mono    (11666):   at Mono.Security.Protocol.Tls.SslStreamBase.BeginWrite (System.Byte[] buffer, Int32 offset, Int32 count, System.AsyncCallback callback, System.Object state) [0x00000] in <filename unknown>:0 
>06-06 14:56:52.799 E/mono    (11666):   at System.Net.WebConnection.BeginWrite (System.Net.HttpWebRequest request, System.Byte[] buffer, Int32 offset, Int32 size, System.AsyncCallback cb, System.O
>The program 'Mono' has exited with code 0 (0x0).
Comment 1 Marek Habersack 2014-07-10 09:09:28 UTC
Can you please provide a minimal test case which reproduces the issue?
Comment 2 PJ 2014-07-10 10:30:14 UTC
It would also be very helpful to clarify the version used here. There is no released version of Xamarin.Android with the version number 4.14.3 or 4.14.4.

The current stable is 4.12.6.1 and the current Alpha is 4.14.0.34.

Since you're reporting a new crash (a regression), I'd like to get to the bottom of this ASAP but we'll need a little bit more information to help get there.
Comment 3 mlpstingray 2014-07-14 10:26:38 UTC
My mistake, the right version numbers are really 4.12.4 and 4.12.3.

So it was failing normally on 4.12.3 and now crash on 4.12.4.


Sorry for the delay of my reply, seems like I missed the update email.
Comment 4 Chris Hardy [MSFT] 2017-06-27 01:55:08 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Android. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.