iOS 5 only crashes about reachability HOT 8 CLOSED

I'll look into this, but one note, you dont need to stop/start the notifier when you go to the background, it'll work fine if you just start it at app startup and leave it running. (which is what I do).

I dont actually have an iOS5 device but I have a couple of theories I'll test.

from reachability.

I start and stop the notifier based on either specific advice from a WWDC session or just the general recommendation to turn off unnecessary things when the app isn't active or foreground - I don't remember which. I assume that it has an impact on battery life as well, but I'm not sure if in reality it does. If there's no effect, I can change that code although there may be other possible issues such as: https://github.com/AFNetworking/AFNetworking/issues/512.

I think the difference is that you schedule the notifications with a queue (SCNetworkReachabilitySetDispatchQueue) and the other Reachability code I've used in the past (Apple Reachability and AFNetworking) schedules them on a runloop (SCNetworkReachabilityScheduleWithRunLoop). Maybe there's an iOS 5 specific issue with SCNetworkReachabilitySetDispatchQueue although I haven't been able to find anyone else reporting it online.

I'm not able to replicate yet, although I do get a few crash reports for this everyday from my iOS 5 users. I've tried testing with an iPad 1 (5.1.1) using the Network Link Conditioner (though an iPhone hotspot) and mixed in some memory warnings as well without luck.

If you have some ideas or theories, let me know. Thanks for your time!

from reachability.

Yeah there is no need (and no effect on battery life) to stop the reachability notifier when moving to background, it was originally build for a VoIP app so it was designed to just stay running all the time (iOS is very clever about background processing)

Reachability was originally designed for iOS5 so unless a new change has broken backwards compatibility it should work fine. If I can find an iOS5 device among my test units I will definitely test it.

from reachability.

Ever find out why this crash occurred? We're having the same issue.

from reachability.

It's an issue with the dispatch queue setup. It happens even if you don't use the queue based reachability methods and only affects iOS 5.

I switched to the following Reachability code and haven't had an crashes since:
https://gist.github.com/darkseed/1182373

from reachability.

Thank @soleares, I'll check it out. We're using iOS5 specifically for a project.

from reachability.

Running into this issue too. This appears to be caused by this reachability library posting notifications on the main thread. If the observers for that notification check reachability status they will invariably be calling SCNetworkReachabilityGetFlags, which according to Apple's Docs should not be called on the main thread because it might require a DNS lookup and could take over 30 seconds and so trigger iOS Application Watchdog, that will kill the app for hanging.

Here's the reference: https://developer.apple.com/Library/ios/samplecode/Reachability/Listings/ReadMe_txt.html

Fix would be to ensure that the observer methods use GCD to react to reachability status on a separate thread.

from reachability.

I'm closing this as I definitely don't support iOS5 any more

from reachability.