Bug 2236 - Try catch around WCF call isnt catching
Summary: Try catch around WCF call isnt catching
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 5.0
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2011-11-28 18:31 UTC by James Clancey
Modified: 2013-12-05 18:36 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 James Clancey 2011-11-28 18:31:47 UTC
A NameResolutionFailure error during an async wcf call is not caught by using a try catch.

This is the client code I have written...



ICrewWS rs=new ICrewWS();

AuthSoapHd clsUC=new AuthSoapHd();






catch(Exception e)


UIAlertView alert=new UIAlertView();

alert.Message="Could not retrieve Blogs. Check for connection and try again"




However no exception is raised, the code is found to fail at which is auto
creaed in the refernce.cs

public Blog[] EndGetBlogs(System.IAsyncResult asyncResult) {

object[] results = this.EndInvoke(asyncResult);

return ((Blog[])(results[0]));

Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-04-04 10:34:22 UTC
You should see the exception in the callBackBlogs callback, the AsyncCompletedEventArgs argument has an Error property which is an instance of WebException for me.
Comment 2 PJ 2013-11-19 17:05:56 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 3 PJ 2013-12-05 18:36:24 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.