-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reachableBlock is not called but internet is online, OSX 10.9.3 #65
Comments
I was having the same problem on iOS 7.1 and your workaround seems to solve it. You should make a pull request unless someone comes up with a better solution! |
created pull request #69 |
i got it. the problem was that i was creating Reachability with full url, not the host. in this case reachability always sends 0 in flags |
I will close this an open an issue to improve the hostname code |
mwkirk
added a commit
to mwkirk/Reachability
that referenced
this issue
Jul 8, 2015
* See tonymillion#65 Signed-off-by: Mark Kirk <[email protected]>
mwkirk
added a commit
to mwkirk/Reachability
that referenced
this issue
May 19, 2016
* See tonymillion#65 Signed-off-by: Mark Kirk <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: