From 8916a10dc4f0aa00bfbd86a6767805b9d0b28ed2 Mon Sep 17 00:00:00 2001
From: Mattt Thompson <m@mattt.me>
Date: Wed, 8 May 2013 10:26:49 -0700
Subject: [PATCH] [Issue #969] Reordering network reachability calls to provide
 correct reachability status on initialization (/thanks @djmadcat)

---
 AFNetworking/AFHTTPClient.m | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/AFNetworking/AFHTTPClient.m b/AFNetworking/AFHTTPClient.m
index 9a33557..f0baeff 100644
--- a/AFNetworking/AFHTTPClient.m
+++ b/AFNetworking/AFHTTPClient.m
@@ -367,7 +367,6 @@ static void AFNetworkReachabilityReleaseCallback(const void *info) {
 
     SCNetworkReachabilityContext context = {0, (__bridge void *)callback, AFNetworkReachabilityRetainCallback, AFNetworkReachabilityReleaseCallback, NULL};
     SCNetworkReachabilitySetCallback(self.networkReachability, AFNetworkReachabilityCallback, &context);
-    SCNetworkReachabilityScheduleWithRunLoop(self.networkReachability, CFRunLoopGetMain(), (CFStringRef)NSRunLoopCommonModes);
 
     /* Network reachability monitoring does not establish a baseline for IP addresses as it does for hostnames, so if the base URL host is an IP address, the initial reachability callback is manually triggered.
      */
@@ -379,6 +378,8 @@ static void AFNetworkReachabilityReleaseCallback(const void *info) {
             callback(status);
         });
     }
+
+    SCNetworkReachabilityScheduleWithRunLoop(self.networkReachability, CFRunLoopGetMain(), (CFStringRef)NSRunLoopCommonModes);
 }
 
 - (void)stopMonitoringNetworkReachability {