Bug 9601 - Exception thrown in NetworkReachability Dispose method
Summary: Exception thrown in NetworkReachability Dispose method
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 6.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-01-16 10:05 UTC by Prashant Cholachagudda
Modified: 2013-11-22 07:41 UTC (History)
3 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 Prashant Cholachagudda 2013-01-16 10:05:59 UTC
From Desk: 23031

Exception occurs when using following code

	// Is the host reachable with the current network configuration
	public static bool IsHostReachable (string host)
		if (host == null || host.Length == 0)
			return false;
		using (var r = new NetworkReachability (host)){
			NetworkReachabilityFlags flags;
			if (r.TryGetFlags (out flags)){
				return IsReachableWithoutRequiringConnection (flags);
		return false;


at MonoTouch.SystemConfiguration.NetworkReachability.Dispose () [0x00000]

at Reachability.IsHostReachable (string) [0x0003e] in

at AgDNA.SyncMgr.SyncFromCloudLowFreqCallback (object) [0x00007] in

at System.Threading.Timer/Scheduler.TimerCB (object) [0x00007] in

at (wrapper runtime-invoke) <Module>.runtime_invoke_void__this___object
(object,intptr,intptr,intptr) <IL 0x00052, 0xffffffff>
Comment 2 Rolf Bjarne Kvinge [MSFT] 2013-01-17 05:16:43 UTC
This is very strange, because there isn't much that can go wrong in NetworkReachability's Dispose method.

Exactly which exception was thrown?
Comment 4 Rolf Bjarne Kvinge [MSFT] 2013-05-27 03:32:46 UTC
@Joseph: Can you get a symbolicated crash report for your crash?
Comment 5 Joseph Hanna 2013-05-27 19:36:10 UTC
How do I do that?
Comment 6 Rolf Bjarne Kvinge [MSFT] 2013-05-28 04:25:55 UTC
You can find crash reports in Xcode's Organizer (open Xcode -> menu Window/Organizer -> and the reports will be found in the Device Logs node under your device on the left). Xcode will try to symbolicate crash reports automatically, but this may fail if you've rebuilt your project since it crashed.
Comment 7 PJ 2013-11-19 17:05:13 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 8 Joseph Hanna 2013-11-19 17:09:48 UTC
I have seen this happen again and I have upgraded versions of Xamarin.iOS and XS several times.

I am happy for you to close this.
Comment 9 Joseph Hanna 2013-11-19 17:11:54 UTC
*haven't seen*
Comment 10 Rolf Bjarne Kvinge [MSFT] 2013-11-22 07:41:03 UTC