when network status changes,the block will always called twice,the first time may be the wrong result.
could this be right?

Hi,

It would be good document that the SystemConfiguration.framework needs to be linked in order for this library to build on iOS.

Is there somewhere to setting it?

First, thanks for making the code available out here.

The Notification is not posted - reachabilityChanged: method is not accessed.
It gets accessed first time when the code runs, then reachabilityChanged: does not respond when internet is turned off and on.
My NotificationCenter is setup in the viewDidLoad: of a View Controller and the reachabilityChanged: code is in the ViewController.m file.
I checked. The View Controller is on the mainThread: . I do have other classes that made asychronous calls (NSURLConnection).
This the only View Controller in the App. My guess is it is not getting released until the App is quit?

code:

• (void)viewDidLoad
  {
  [super viewDidLoad];

  DEBUG_LOG(@"is Main thread? %d", [NSThread isMainThread]);

  Reachability *reach = [Reachability reachabilityWithHostname:INTERNETCHECK_URL];

  // setup Internet availibility notification
  

  [[NSNotificationCenter defaultCenter] addObserver:self
  selector:@selector(reachabilityChanged:)
  name:kReachabilityChangedNotification
  object:nil];
  [reach startNotifier];

  if ([reach isReachable]) // works fine!
  {
  // do blah blah
  }

I haven't looked extremely thoroughly, but I am getting a seemingly straightforward static analysis warning as seen in the screenshot here:

I certainly wouldn't mind attempting to fork, patch and pull-request if you'd like, I just wanted to make sure it wasn't intentionally left that way. It doesn't seem that anyone else has brought it up as an issue, so it seemed worth asking.

Thanks!

I've downloaded repo and changed demo app, so it uses "reachabilityWithAddress" instead of "reachabilityWithHostname".
Here is code:

struct sockaddr_in callAddress;
callAddress.sin_len = sizeof(callAddress);
callAddress.sin_family = AF_INET;
callAddress.sin_port = htons(8001);
callAddress.sin_addr.s_addr = inet_addr("192.168.2.101");
Reachability *reach = [Reachability reachabilityWithAddress:&callAddress];

But it doesn't work.

Is it bug or am I doing something wrong ?

Thanks.

Hello I tried in Iphone 4S and worked well, and then I tried in a Iphone 4 , and the app crash

Regards

Hi, @tonymillion :

I don't known whether it will leak?

+(Reachability *)reachabilityWithAddress:(const struct sockaddr_in *)hostAddress 
{
    SCNetworkReachabilityRef ref = SCNetworkReachabilityCreateWithAddress(kCFAllocatorDefault, (const struct sockaddr*)hostAddress);
    if (ref) 
    {
        id reachability = [[self alloc] initWithReachabilityRef:ref];

#if __has_feature(objc_arc)
        return reachability;
#else
        return [reachability autorelease];
#endif
    }

    return nil;
}

Whether must release the ref?

Just ran across this project and it looks interesting. What is the behavior of an unresolvable host name, i.e., what happens if I use a host name in reachabilityWithHostname where the host name has no IP address from DNS?

Thanks in advance.

Using
[Reachability reachabilityWithHostname:hostName]
if the the host name is an ip address the reachable block never gets called. The isReachable call works. Is this intended behaviour or an issue with status notifications?

I installed your library through cocoapods and it crashes immediately on iOS 4.3 when I call [Reachability reachabilityForInternetConnection]; This crash does not happen when running iOS 5.0 or 5.1. The following is printed to the debug log:

dyld: lazy symbol binding failed: Symbol not found: _objc_storeStrong
Referenced from: /Users/jibanez/Library/Application Support/iPhone Simulator/4.3.2/Applications/131AA5F6-A629-445D-91E4-D5575CEF9C11/[App].app/[App]
Expected in: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.3.sdk/System/Library/Frameworks/Foundation.framework/Foundation

dyld: Symbol not found: _objc_storeStrong
Referenced from: /Users/jibanez/Library/Application Support/iPhone Simulator/4.3.2/Applications/131AA5F6-A629-445D-91E4-D5575CEF9C11/[App].app/[App]
Expected in: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.3.sdk/System/Library/Frameworks/Foundation.framework/Foundation

The actual crash is happening on line 139, in - (Reachability *)initWithReachabilityRef:(SCNtworkReachabilityRef)ref, self = [super init];.

I've done some research and it appears it may be related to ARC. CocoaLumberjacks had a similar sounding issue. The rest of the project does not have ARC enabled, and Reachability.m has the -fobjc-arc flag.

I realize that if this is, in fact, an LLVM issue, there may not be much you can do about it. Is there a previous version I can use that does not use ARC?

I am using reachabilityWithHostName in conjunction with start notifier to check for a connection (hostname = www.google.com) in a production app. This appears to be quite robust, working ~99% of the time.

HOWEVER, I have seen a handful a failures where reachability seems to always report no connection, even when the connection is available and valid. This persists even after an app close / restart (creating an entirely new reachability instance in the process.) In such cases, restarting the entire iOS device immediately solves the problem.

I am looking for theories here. All I can come up with is that something must be getting cached at the iOS system level. Perhaps a bad DNS entry or something? (Maybe do to public wifi login pages, etc.?) Anyone else seen this?

I am getting this error upon calling [Reachability startNotifier] function.

Here is my code snippet:

Reachability *r = [Reachability reachabilityWithHostname:host];    
r.reachableBlock = ^(Reachability*reach)
{
    // Update the UI on the main thread

    });
};    
r.unreachableBlock = ^(Reachability*reach)
{
    // Update the UI on the main thread with error alert

    });
};    
[r startNotifier];    

I can very well browse the host from Safari. What maybe the issue?
None of the success/failure blocks above get called.

I have an app which uses Reachability. The app runs on iOS 6.1 onwards. Everything works fine in iOS version prior to iOS 7.1. In iOS 7.1, the following problems occur.

1. kReachabilityChangedNotification does not get called.
2. currentReachabilityStatus isn't working. I have my Wi-Fi turned off and run the app where it calls reachabilityForInternetConnection and it returns reachable.

The above issues only occur in iOS 7.1. I downloaded and added the latest class files but to no avail.

Any way to fix these?

Any way to fix that?

In your startNotifier you do a dispatch_release(), which is not valid. Whether or not the method itself retains the queue is immaterial. You only "own" the refcount from your create. When you stop listening, you can destroy the queue with a dispatch_release.

Static Analyzer reports warnings for iOS7 deployment target.

dodikk$ xcodebuild -version
Xcode 5.0.2
Build version 5A3005

-censored-

Sorry, never mind. The issue cleared up. Probably a network blip or something.

Tony,
I am unable to access your Reachability library since you merged in the new arc warning changes. Here is what happens when I try and pull a copy of your repo.

OSroX: ~/Dropbox/Projects$ git clone git://github.com/tonymillion/Reachability.git
Cloning into 'Reachability'...
error: cannot fork() for index-pack: Resource temporarily unavailable
fatal: fetch-pack: unable to fork off index-pack

Can you check things out and see if something went amiss with the latest merge?

Thanks
Brian

Was using :

self.reachability = [Reachability reachabilityWithHostname:hostNameString];
[self.reachability startNotifier];


All looked good at first.
Reachability reported a successful link to the website.

But when I left the app running in the simulator and dropped out to the Terminal to disabled/re-enabled the Ethernet port using :

sleep 5
networksetup -setnetworkserviceenabled "Thunderbolt Ethernet" off
sleep 10
networksetup -setnetworkserviceenabled "Thunderbolt Ethernet" on


Things started to go wrong.
Reachability detected the network disappearing but didn't detect when it came back.
Even after Safari started working again, still no response from Reachability.

Strangely, Reachability would detect the returning network if I did :

networksetup -setairportpower en0 on
sleep 10
networksetup -setairportpower en0 off


However…
I did manage to get things working in the end.
By changing :

[Reachability reachabilityWithHostname:hostNameString];

to

[Reachability reachabilityForInternetConnection];


Installed it via cocoapods. Opened the generated workspace and I'm getting the following error:

Reachability.m:41:1: Property with 'retain (or strong)' attribute must be of object type

I've checked and NEEDS_DISPATCH_RETAIN_RELEASE is 0 which is correct because my deployment target is 6.0 and I'm building with Xcode 4.6.

Any ideas what might be wrong?

Thanks!

Hi Tony, can you add a check that if we already started the notifier to ignore further calls to the method? I'm seeing error text in the console right now. I have multiple threads attempting download and they'll all fail at nearly the same time, but either one of them can call startNotifier upon failure. This just lets me avoid creating my own global variable to track this :P

This class is working well, but I get two false positives consistently. I’ve tried both blocks and NSNotification. The behavior is the same.

1. When the application launches and calls startNotifier, a notification for the current connection state is posted, even though nothing has changed.
2. When a connection is re-established, there’s an “unreachable” notification immediately before the “reachable” one.

I imagine most people are updating some internal state or changing something in the UI, so redundant notifications aren’t a big deal. I’m trying to use this for Quicksilver’s Event Triggers plug-in so users can fire off an arbitrary command when the connection state changes. You wouldn’t want such a trigger running at application launch, and you wouldn’t want a “disconnected” trigger running every time a connection is re-established.

For what it’s worth, I was able to reproduce this in a new stand-alone project.

This is a semi-duplicate of #59, but for me, it’s every single time.

Thanks.

OS X 10.9.1
Xcode 5.0.1
SDK 10.9

I have my call to Reachability in applicationDidFinishLaunchingWithOptions.

If my connection is really bad and I launch the app, the isReachable check takes about 30 seconds and crashes the app with a "the application failed to launch in time" error message. To reproduce what I'm seeing, go to Settings.app -> Developer -> Network Link Conditioner, turn it on and set it to 100% loss.

my code is as follows:

if ( reachHost == nil )
{
reachable = NO;
reachHost = [Reachability reachabilityWithHostname:@"www.google.com"];
reachable = [reachHost isReachable];

    reachHost.reachableBlock = ^(Reachability * reachability)
    {
        dispatch_async(dispatch_get_main_queue(), ^{
            reachable = YES;
        });
    };

    reachHost.unreachableBlock = ^(Reachability * reachability)
    {
        dispatch_async(dispatch_get_main_queue(), ^{
            reachable = NO;
        });
    };

    [reachHost startNotifier];
}

Is there any way to get around this crash? Thanks for your help!

This implementation conflicts with ShareKit's Reachability class. For compatibility I had to rename class to something like ReachabilityARC.

The reachableBlock is only called after disconnecting and reconnecting network.
What am I missing?

-(BOOL)application:(UIApplication *)application willFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
    Reachability * internetReachability = [Reachability reachabilityForInternetConnection];
    internetReachability.reachableBlock = ^(Reachability * reachability)
    {
        NSLog(@"Reachable");
    };
    internetReachability.unreachableBlock = ^(Reachability * reachability)
    {
        NSLog(@"Not Reachable");
    };
    [internetReachability startNotifier];
    return YES;
}

It always show this info

I'm making a Mac application an I'm trying to use the reachability library.

Problem is that the reachability always turns out as unreachable for some reason.

I've downloaded the demo app and when I run that, it turns out reachable (as it should) and it works perfectly in any other way.

What can I have done in my app that stops the reachability library for checking correctly?

Edit
It doesn't register when I jump off the internet either. It registers when I jump back on, but notifies me as being unreachable.

What can cause this

XCode Version 4.6 (4H127)
Deployment Target 6.1

Any ideas?

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c -arch i386 -fmessage-length=0 -std=gnu99 -Wno-trigraphs -fpascal-strings -Os -Wno-missing-field-initializers -Wno-missing-prototypes -Wno-return-type -Wno-implicit-atomic-properties -Wno-receiver-is-weak -Wformat -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function -Wno-unused-label -Wno-unused-parameter -Wno-unused-variable -Wunused-value -Wno-empty-body -Wno-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wno-constant-conversion -Wno-int-conversion -Wno-enum-conversion -Wno-shorten-64-to-32 -Wpointer-sign -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wno-undeclared-selector -Wno-deprecated-implementations -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator6.1.sdk -fexceptions -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -g -Wno-sign-conversion -fobjc-abi-version=2 -fobjc-legacy-dispatch -mios-simulator-version-min=6.0 -iquote /Users/spierce/code/test_ios/vendor/Pods/build/Pods.build/Release-iphonesimulator/Pods.build/Pods-generated-files.hmap -I/Users/spierce/code/test_ios/vendor/Pods/build/Pods.build/Release-iphonesimulator/Pods.build/Pods-own-target-headers.hmap -I/Users/spierce/code/test_ios/vendor/Pods/build/Pods.build/Release-iphonesimulator/Pods.build/Pods-all-target-headers.hmap -iquote /Users/spierce/code/test_ios/vendor/Pods/build/Pods.build/Release-iphonesimulator/Pods.build/Pods-project-headers.hmap -I/Users/spierce/code/test_ios/vendor/Pods/.build/include -I/Users/spierce/code/test_ios/vendor/Pods/BuildHeaders -I/Users/spierce/code/test_ios/vendor/Pods/BuildHeaders/Reachability -I/Users/spierce/code/test_ios/vendor/Pods/build/Pods.build/Release-iphonesimulator/Pods.build/DerivedSources/i386 -I/Users/spierce/code/test_ios/vendor/Pods/build/Pods.build/Release-iphonesimulator/Pods.build/DerivedSources -F/Users/spierce/code/test_ios/vendor/Pods/.build -fobjc-arc -DOS_OBJECT_USE_OBJC=0 -include /var/folders/tz/4q_gzxkn2n5cfzl3sn70nnh00000gn/C/com.apple.Xcode.501/SharedPrecompiledHeaders/Pods-prefix-btctoghzdwrrupevhwmcptathcsu/Pods-prefix.pch -MMD -MT dependencies -MF /Users/spierce/code/test_ios/vendor/Pods/build/Pods.build/Release-iphonesimulator/Pods.build/Objects-normal/i386/Reachability.d --serialize-diagnostics /Users/spierce/code/test_ios/vendor/Pods/build/Pods.build/Release-iphonesimulator/Pods.build/Objects-normal/i386/Reachability.dia -c /Users/spierce/code/test_ios/vendor/Pods/Reachability/Reachability.m -o /Users/spierce/code/test_ios/vendor/Pods/build/Pods.build/Release-iphonesimulator/Pods.build/Objects-normal/i386/Reachability.o
/Users/spierce/code/test_ios/vendor/Pods/Reachability/Reachability.m:41:1: error: property with 'retain (or strong)' attribute must be of object type
@property (nonatomic, strong) dispatch_queue_t          reachabilitySerialQueue;
^
1 error generated.

https://gist.github.com/a9c67e87e573fffafbbc

Hi

These are the two errors that I don't understand why happens:

"OBJC_CLASS$_Reachability", referenced from:

Objc-class-ref in FReachViewController.o

Symbol(s) not found for architecture armv7

Linker command failed with exit code 1 (use -v to see invocation)

Can you help me?
Vitor Ferreira

I have my call to Reachability in applicationDidFinishLaunching. If my connection is really bad and I launch the app, Reachability takes forever and crashes the app with a "the application failed to launch in time" error message. To reproduce what I'm seeing, go to Settings.app -> Developer -> Network Link Conditioner, turn it on and set it to 100% loss.

Is there any way to get around this crash? Thanks for your help!

I want to check a server is live or not with ip, for example, 74.125.71.104 (Google's ip)

// allocate a reachability object
struct sockaddr_in address;
address.sin_len = sizeof(address);
address.sin_family = AF_INET;
address.sin_port = htons(80);
address.sin_addr.s_addr = inet_addr("74.125.71.104");

Reachability *reach = [Reachability reachabilityWithAddress:&address];

but those not working.

When I change to reachabilityWithHostname, it's working.

I am having the same issue is this http://stackoverflow.com/questions/19367351/tony-million-reachability-says-unreachable-when-connected

I tried to fix by using a delay for the code called in the unreachable block, but then cancel all delayed method calls if reachableBlock is called.

This is huge problem!

Hi! Per the README, I set up a Reachability notifier using the Block example.

When I run my app, it blows up at line 512, after the postNotificationName:object: invocation:

// this makes sure the change notification happens on the MAIN THREAD
dispatch_async(dispatch_get_main_queue(), ^{
    [[NSNotificationCenter defaultCenter] postNotificationName:kReachabilityChangedNotification 
                                                        object:self];
});

CoreFoundation`-[NSObject(NSObject) doesNotRecognizeSelector:]:, specifically.

Any ideas? I'm stumped. :(

just thought I'd mention that Apple's Reachability uses:
reachabilityWithHostName

with uppercase 'Name' whereas in this class it's:
reachabilityWithHostname

So it's not a 100% drop-in replacement. ;)

In my network I need to authenticate before having 'real' access to the internet. Before that authentication I can resolve DNS hostnames to IP but not more.

Reachability always tells me that I am connected as long as I get an DNS reply. There should be an option to check e.g. with a ping request or maybe even do a HEAD http request to see if we have 'real' internet.

-(void)dealloc
{
[self stopNotifier];

if(self.reachabilityRef)
{
    CFRelease(self.reachabilityRef);
    self.reachabilityRef = nil;
}

if !(__has_feature(objc_arc))

[super dealloc];

endif

}

and *.h you define like :
@Property (nonatomic, copy) NetworkReachable reachableBlock;
@Property (nonatomic, copy) NetworkUnreachable unreachableBlock;

please release reachableBlock & unreachableBlock when sb not use ARC

https://github.com/willonboy

The current version of code doesn't work when compiled under ARC on Xcode 4.5
Turning off ARC means, there would be memory leaks.

Hi i am using Reachability Block on applicationDidFinishedLaunching and that it shows a pop up over class. But out of many ViewControllers there are some ViewControllers where downloaded data is placed and there is no need of Internet. So, i want that the Block Code Does not work there? Is there any proper way of doing it?

When I triying to build my little project with this especification one error appear

Reachability.m:41:1: Property with 'retain (or strong)' attribute must be of object type

This is my PodFile:

platform :ios, '6.0'

pod 'RCLocationManager', :head
pod 'MagicalRecord', '2.0.8'
pod 'Parse', '1.1.32'
pod 'Reachability', :head
pod 'SSKeychain', '0.2.1'
pod 'JASidePanels', '~> 1.3.0'
pod 'NewRelicAgent', '1.0.0'

Any idea what is happens or how I solve it?

Thanks :)

if you setup Reachability for localwifi mode it won't notify the connection state after execution. Just until a connect or disconnect happen.

Would be great to specify license type and add LICENSE file to repo.
Thanks.

I've noticed that TMReachabilityCallback is called with flags == 0 if there is a existing internet connection via wifi on os x mavericks, i think you should add a workaround like this:
-(BOOL)isReachableWithFlags:(SCNetworkReachabilityFlags)flags
{
if (flags == 0)
return YES;

Maybe there is a better solution, but TMReachabilityCallback is called only once

My app reject which the reason is protoc: __bzero.
How to resolve?

If a project prodfile specifies IOS6+ as a deployment target, Reachibility.m will fail to compile.

This is due to OS_OBJECT_USE_OBJC=0 which gets set because the podspec targets IOS5 + no-ARC. However NEEDS_DISPATCH_RETAIN_RELEASE will also be 0 because it only checks the deployment target and not OS_OBJECT_USE_OBJC. As a result dispatch_queue_t is a struct and not object -> boom goes the compiler.

Quick fix would be to check OS_OBJECT_USE_OBJC as well, however it doesn't feel right as I would want proper ARC support in IOS6+.

Getting this when I try to archive my app:

Xcode 4.3.2, building Mac app

I am trying to use your class to check my reachability to a local IP address like so:

hostReach = [Reachability reachabilityWithHostname:@"192.168.2.113"];

But this never gets to execute my reachable and unreachable blocks. The same goes for internet connection:

internetReach = [Reachability reachabilityForInternetConnection];

It will not execute my reachable or unreachable blocks. And I know for certain that I have reachability to both those hosts.

I am running on the simulator.

My object registers for reachabilityChanged notification, creates a Reachability instance with host (and retains it).
I am toggling airplane mode on and off on a device with WiFi only (no 3G).
In addition to reachabilityChanged, I check the network status on UIApplicationDidBecomeActive (Because I have to go to the settings screen and back).

currentNetworkStatus ALWAYS returns NotReachable... I tried my server's address and also http://google.com...
But I can visit websites in Safari.

Sorry for the FAQ format...

Haven't tried with blocks yet.

When the WIFI is connected, but not login (For example, in hotels, you need to login beforehand), reachabilityWithHostName will try nearly 10 seconds to try. Is there any way to set a timeout (I think 10 seconds is too long)?

For some reason TMReachabilityCallback never gets triggered on iOS7.
Tried it only in simulator, thou...

My users are sometimes getting iOS 5 only crashes. I started seeing these after switching from Apple's Reachability 2.2 to this library so I think it may be related to the GCD additions which I'm not using.

Here's how I use it:

• Call startNotifier in applicationDidBecomeActive:
• Call stopNotifier in applicationWillResignActive:
• Use the notification only and do not check the status directly.

The crash occurs soon after the app becomes active, but it don't think the watchdog killed it (no "ate bad food" 0x8badf00d). It looks like the crash is in the SCNetworkReachability XPC service.

I'm not able to reproduce it myself after a lot of testing (bad network, memory warnings, etc) so I'm hoping that someone has further insight. Here's the relevant part of the crash log:

OS Version: iPhone OS 5.1.1 (9B206)
Report Version: 104

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000008
Crashed Thread: 7

Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0:
0 libsystem_kernel.dylib 0x35b32054 semaphore_wait_trap + 8
1 libdispatch.dylib 0x33e66158 _dispatch_semaphore_wait_slow + 184
2 libdispatch.dylib 0x33e66188 dispatch_semaphore_wait$VARIANT$up + 28
3 libxpc.dylib 0x3227889a xpc_connection_send_message_with_reply_sync + 206
4 SystemConfiguration 0x339d4be6 _reach_server_target_status + 938
5 SystemConfiguration 0x339d5d56 __SCNetworkReachabilityServer_targetStatus + 14
6 SystemConfiguration 0x339beaee __SCNetworkReachabilityGetFlags + 198
7 SystemConfiguration 0x339bf9ca __SCNetworkReachabilityScheduleWithRunLoop + 826
8 SystemConfiguration 0x339bfe38 SCNetworkReachabilitySetDispatchQueue + 80
9 mrl 0x0005f2e8 -Reachability startNotifier
10 mrl 0x0004247a -AppDelegate startReachability
11 mrl 0x0003f03c -AppDelegate applicationDidBecomeActive:
12 UIKit 0x33210c2a -[UIApplication _stopDeactivatingForReason:] + 182
13 UIKit 0x332a84f2 -[UIApplication _handleApplicationResumeEvent:] + 1510
14 UIKit 0x331ccafc -[UIApplication handleEvent:withNewEvent:] + 1068
15 UIKit 0x331cc560 -[UIApplication sendEvent:] + 48
16 UIKit 0x331cbf34 _UIApplicationHandleEvent + 5820
17 GraphicsServices 0x337be224 PurpleEventCallback + 876
18 CoreFoundation 0x35aa051c CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION + 32
19 CoreFoundation 0x35aa04be __CFRunLoopDoSource1 + 134
20 CoreFoundation 0x35a9f30c __CFRunLoopRun + 1364
21 CoreFoundation 0x35a2249e CFRunLoopRunSpecific + 294
22 CoreFoundation 0x35a22366 CFRunLoopRunInMode + 98
23 GraphicsServices 0x337bd432 GSEventRunModal + 130
24 UIKit 0x331facce UIApplicationMain + 1074
25 mrl 0x0003e79e main (main.m:16)
26 mrl 0x0003e738 start + 32

Thread 7 name: Dispatch queue: com.apple.SystemConfiguration.SCNetworkReachability.xpcq
Thread 7 Crashed:
0 libdispatch.dylib 0x33e669e8 _dispatch_retain$VARIANT$up + 0
1 libdispatch.dylib 0x33e644f8 dispatch_group_async_f$VARIANT$up + 16
2 SystemConfiguration 0x339be7e2 __SCNetworkReachabilityPerform + 126
3 SystemConfiguration 0x339d5128 ___reach_connection_create_block_invoke_1 + 320
4 libxpc.dylib 0x3227d8c2 XPC_CONNECTION_EVENT_HANDLER_CALLOUT + 30
5 libxpc.dylib 0x32276d5c _xpc_connection_recv_message + 500
6 libxpc.dylib 0x32276b18 _xpc_connection_wakeup_recv + 160
7 libxpc.dylib 0x322769b8 _xpc_connection_wakeup2 + 1264
8 libxpc.dylib 0x322763f6 _xpc_connection_wakeup + 62
9 libdispatch.dylib 0x33e67252 _dispatch_source_invoke + 510
10 libdispatch.dylib 0x33e64b1e _dispatch_queue_invoke$VARIANT$up + 42
11 libdispatch.dylib 0x33e64c3e _dispatch_queue_drain + 166
12 libdispatch.dylib 0x33e64b12 _dispatch_queue_invoke$VARIANT$up + 30
13 libdispatch.dylib 0x33e64c3e _dispatch_queue_drain + 166
14 libdispatch.dylib 0x33e64b12 _dispatch_queue_invoke$VARIANT$up + 30
15 libdispatch.dylib 0x33e65784 _dispatch_worker_thread2 + 208
16 libsystem_c.dylib 0x34ce5df4 _pthread_wqthread + 288
17 libsystem_c.dylib 0x34ce5cc8 start_wqthread + 0