evie/AFNetworking
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

[Issue #969] Reordering network reachability calls to provide correct reachability status on initialization (/thanks @djmadcat)

Browse source
This commit is contained in:
Mattt Thompson 2013-05-08 10:26:49 -07:00
parent c3db232a5e
commit 8916a10dc4
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
AFNetworking/AFHTTPClient.m
View file

@ -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 {