SCNetworkReachabilityGetFlags returns 0 even when wireless available

Question

I have an app that uses Apples reachability code. When I tab out of the app, turn on airplane mode, go back into the app, I correctly get a message that says no connection is available. If I go back out turn OFF airplane mode and go back into the app, I STILL get the message that no connection is available. The specific problem code is this:

NetworkStatus status = kNotReachable;
if (SCNetworkReachabilityGetFlags(reachabilityRef, &flags))
{
    status = [self networkStatusForFlags: flags];
    return status;
}

I get inside the if statement and flags ends up being 0 (kSCNetworkReachabilityFlagsTransientConnection). What does that mean exactly? Has anyone experienced this and does anyone know a work-around or fix? Been playing with it for hours...

kSCNetworkReachabilityFlagsTransientConnection has the value 1<<0 (which is 1). You are getting 0, which means none of the flags are set. — jhabbott, Jan 06 '12 at 17:21
@Sandeep I think the problem was with some really bad corporate WiFi. I haven't seen the problem in over a year now. — jjxtra, Apr 25 '13 at 20:54
@PsychoDad Can u please paste the code or explain what you did different than the code mentioned above — Sandeep, Apr 25 '13 at 21:44
Code has not changed and is the same as what is in the question — jjxtra, Apr 25 '13 at 22:07

score 11 · Accepted Answer · answered Jan 06 '12 at 18:10

11

I have found that this is caused by supplying a hostname with a protocol specifier (such as http://hostname instead of just hostname). Try specifying just the hostname by itself to see if this fixes your problem.

answered Jan 06 '12 at 18:10

jhabbott

18,461
9
58
95

1

This solved the issue for me. I was checking with Reachability for a website to load in a UIWebView. By using the website domain for Reachability purposes, but then using the same domain prepended by protocol for UIWebView loading purposes, all worked fine again. Why it worked prior, I'm not sure. Seems to have become more finicky for me after the iOS5.1.1 update. Good advice @jhabbott! – idStar May 23 '12 at 15:17
We are using only the host name and always have been. I believe the real problem was some really bad corporate WiFi. – jjxtra Apr 25 '13 at 20:56
1

Since this solved the problem for some people, I'll accept this answer. – jjxtra Aug 05 '14 at 16:21
Thanks a lot! As I noticed it should be "root" hostname without subdirectories. – Tzoiker Jul 27 '15 at 11:15

score 3 · Answer 2 · answered Jan 17 '13 at 14:24

After you call SCNetworkReachabilityGetFlags it is important also to call CFRelease to avoid caching the network status. See my implementation below:

SCNetworkReachabilityRef reachability = SCNetworkReachabilityCreateWithName(NULL, host_name);

SCNetworkReachabilityFlags flags;
success = SCNetworkReachabilityGetFlags(reachability, &flags);
bool isAvailable = success && (flags & kSCNetworkFlagsReachable) &&
!(flags & kSCNetworkFlagsConnectionRequired);
CFRelease(reachability);
if (isAvailable) {
    NSLog(@"Host is reachable: %d", flags);
    return true;
}else{
    NSLog(@"Host is unreachable");
    return false;
}

This answer solved my problem. Apple really should mention this in their documents. — Eddie Deng, Oct 11 '15 at 06:46

score 0 · Answer 3 · answered Aug 01 '17 at 10:23

0

I had the same problem but it was only happening when i was testing in the simulator. I spent 2 days going crazy and then I tested on the device and it worked as a charm! No idea why...

answered Aug 01 '17 at 10:23

Adriana

225
3
8

score 0 · Answer 4 · answered May 16 '11 at 19:16

If the flags were received and they end up being 0, as you've seen, this indicates Airplane Mode is on. However, the results of this check seem to be cached, at least for a short time. Try this: leave your app, turn Airplane Mode off, hit a site in Mobile Safari, then return to your app. This may invalidate the cache.

SCNetworkReachabilityGetFlags returns 0 even when wireless available

4 Answers4

Linked

Related