Bug 6364 - NetworkReachability
Summary: NetworkReachability
Status: RESOLVED DUPLICATE of bug 6309
Alias: None
Product: iOS
Classification: Xamarin
Component: Samples ()
Version: 5.2
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-08-02 08:19 UTC by Allen Holman
Modified: 2012-10-24 19:40 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 DUPLICATE of bug 6309

Description Allen Holman 2012-08-02 08:19:45 UTC
Description of Problem:

NetworkReachability.TryGetFlags(out flags) hangs.  I have an allinone mac and just loaded OS X Lion.  


Steps to reproduce the problem:
1. 
NetworkReachabilityFlags flags = NetworkReachabilityFlags.Reachable;
				
NetworkReachability r = new NetworkReachability (host);
r.TryGetFlags(out flags); // This call hangs!!

return IsReachableWithoutRequiringConnection (flags);
 


Actual Results:

Hangs

Expected Results:

return the flags

How often does this happen? 

Always

Additional Information:
Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-10-24 19:40:17 UTC

*** This bug has been marked as a duplicate of bug 6309 ***