iOS4 front & rear ViewControllers lifecycle methods issue about pkrevealcontroller HOT 2 CLOSED

As I've already pointed out here you are indeed correct. All the "fix" did was include defensive programming, but those methods still need to be called manually on iOS 4 seeing how by not attaching them to the view hierarchy, they can never receive those calls.

It seems an iOS 4 compliant version of the controller is something quite a few people want but so far I've been reluctant to implement it seeing how it's more or less a hack. Besides iOS 5 adaption amongst consumers was insanely fast. Seeing how all iOS 4 devices can run iOS 5 as well and with representative studies saying that three weeks after its release 30%~ of the eligible devices were already running iOS 5 (That was sometime in November of 2011.),... I'm not sure whether iOS 4 compatibility is that big of a deal. Although iOS 3.1.3 compatibility is certainly more interesting....

But I'll look into it and maybe reconsider.

from pkrevealcontroller.

FWIW, the iPhone 3G is supported running iOS 4.2 reeeallly slooowwwllly but not iOS 4.3 or iOS 5. Not sure if that colors your thinking at all.

I agree that iOS 4 compliance will be a hack (since iOS 4 really doesn't like having more than one ViewController on the screen at once) and that it's probably not worth it.

from pkrevealcontroller.