CODEWITHSUNDEEP
iphoneobjective-c
stoutyhk
stoutyhk

Reputation: 243

Reachability sometimes fails, even when we do have an internet connection

I've searched but can't see a similar question.

I've added a method to check for an internet connection per the Reachability example. It works most of the time, but when installed on the iPhone, it quite often fails even when I do have internet connectivity (only when on 3G/EDGE - WiFi is OK).

Basically the code below returns NO.

If I switch to another app, say Mail or Safari, and connect, then switch back to the app, then the code says the internet is reachable. Kinda seems like it needs a 'nudge'.

Anyone seen this before? Any ideas?

Many thanks James

+ (BOOL) doWeHaveInternetConnection{

BOOL success;
// google should always be up right?!
const char *host_name = [@"google.com" cStringUsingEncoding:NSASCIIStringEncoding];

SCNetworkReachabilityRef reachability = SCNetworkReachabilityCreateWithName(NULL,
                                                                            host_name);
SCNetworkReachabilityFlags flags;
success = SCNetworkReachabilityGetFlags(reachability, &flags);
BOOL isAvailable = success && (flags & kSCNetworkFlagsReachable) && !(flags & kSCNetworkFlagsConnectionRequired);

if (isAvailable) {
    NSLog(@"Google is reachable: %d", flags);
}else{
    NSLog(@"Google is unreachable");
}

return isAvailable;

}

Upvotes: 8

Views: 7201

Answers (4)

stoutyhk
stoutyhk

Reputation: 243

+ (BOOL) doWeHaveInternetConnection2{
         if([[Reachability sharedReachability] internetConnectionStatus] == NotReachable) {
                   return NO;
          }
          else
          {
                  return YES; 
          }

}

(sorry, code format didn't work in comment)

Upvotes: 1

sehugg
sehugg

Reputation: 3605

What I have found is that you have to be aware of what thread (runloop) from which you first call startNotifier. If you call it from a background thread or NSOperation, you will start the notifier loop on that thread's run loop.

If you share instances, perhaps grabbing a singleton like in [Reachability reachabilityForInternetConnection], it appears from the current code (2.0) that the last invoker wins and gets the notifier set to its run loop.

Upvotes: 1

stoutyhk
stoutyhk

Reputation: 243

With version 2, code should be:

+ (BOOL) doWeHaveInternetConnection2{

if([Reachability reachabilityForInternetConnection] == NotReachable) {
    return NO;
}
else
{
    return YES; 
}

}

Upvotes: 1

Matt Long
Matt Long

Reputation: 24466

Looks like you've stripped out some basic reachability code from the Apple example code. What happens when you leave it intact and do this?

Reachability *hostReach = [[Reachability reachabilityWithHostName: @"www.apple.com"] retain];

NetworkStatus netStatus = [hostReach currentReachabilityStatus];

if (netStatus == NotReachable)
{
    NSLog(@"NotReachable");
}

if (netStatus == ReachableViaWiFi)
{
    NSLog(@"ReachableViaWiFi");
}

if (netStatus == ReachableViaWWAN)
{
    NSLog(@"ReachableViaWWAN");
}

Upvotes: 7

Related Questions