iOS8 Weirdness Part1: UIPopoverController
As and old wolf programmer with years of expirence in iOS I survive most of big iOS updates including switch from 4.2 to 5, from 5 to 6 and so on. Some people remember time when your app was able to work fine on all iOS verions, but all of that changes with iOS7 it makes a big change to how app are made. There is no more easy way to support iOS6 and iOS7 in one app. Apple make new iOS7 API really cool, now we have truly working Interface Builder, StoryBoards, Autolayouts etc. Making apps was never easier before. iOS8 looks event almost the same, so what could possibly go wrong?…
Actually, a lot of things… But you say: “oh comone, it not so bad at all. The era of dirty hacks is away!” - NOPE.
With iOS8 Apple introduced new way to handle
UIPopoverController by introducing brand new
UIAlertController, but as we all know sometimes when you build big app that is developed for few months it is not an easy decision to drop support for specified iOS version… So let’s support both! Of course we are not allowed to use new stuff, we still want our app to support iOS7 so we are not touching our code in terms of rewriting to new popovers and alerts.
If you prefer setuping popovers from code this article is not propably for you but if you are “modern” like me and you cannot anymore live without storyboards and segues you will be suprised what amazing new “features” iOS8 may bring to your iPad Application. Imagine this scenario: You are building your iPad app which require from you to select some values, so the natural way to handle that is to present data set in popover. Now let’s say my app is some kind of alarm app so i need to setup and display time. I build my app and it works like a harm, no rocket sience here it’s a simple one view controller app that fire up UIStoryBoardPopoverSegue when button gets pressed. The image explain app flow (look carefuly your popover segue is now set as deprecated in xCode 6 coz you should use new one which we can’t use due to iOS7 support) so the app will works as described below:
a) User can press “Set my date!” button which opens Popover with DatePicker (sets ‘now’ if date does not exist)
b) User can select date
c) By dimissing popover user is able to set new date
d) If user press button again popover will open with latest date selected
If we run the app on iOS7 this is what we will get:
Ok time for some code, honestly there not to much to explain. First let’s see how do we implement our DatePicker Controller:
1 2 3 4 5 6 7 8
So regular UIViewController with UIDatePicker attached via Outlet, now let’s see what does it actually do:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
As we can expected not to much it is very simple VC that only sets and gets seleted date by overwriting setter and getter of our date property.
Now the main logic:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
As I said not much to explain simply we are passing date if exist to our created
UIPopoverController which is supplied by
UIStoryboardPopoverSegue at the moment we pressed button. We also set ourselfs as delegate so we can respond to popover dimiss. So after it disappear we can set currently selected value and update button title.
Now guess what happens if you try to run this on iOS8 Device / Simulator ? Yes it will stop working :) Value will not update, button title will stay the same, basically madness and tons of WTF per minute.
So where is the problem ? If you set breakpoint in any of delegate methods you will see that they are actually not called, not at all… So the next line that we may be interested is:
1 2 3
Setting the actual delegate, looks fine even if you go deeper and check StoryboardSegue you will see this:
1 2 3 4 5 6 7 8 9 10
So it looks like
UIPopoverController is retained and all is ok! The truth is that is not, i cannot explain why is this happening but after we assign our delegate the connection is droped like the popover has weak reference in the segue… The way to fix that without doing whole loading from code is to simply assing popover to strong variable, so the quick fix for that is:
1 2 3 4 5 6 7 8
And in our segue:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
if you compile this, you will notice that delegate methods are now finally called so one win achieved!, title is updating but… Oh wait why every time i open popover the date is the same ?! Yes we are half done here in iOS7 at the segue all VC are loaded. In iOS8 viewDidLoad is called after segue, so if you will set breakpoint in this line:
1 2 3 4 5 6 7 8 9
So we need one final workaround for this, and there are 2 ways to do that first one:
If you VC do not need to load many variables its a good idea to set some temporary variable that will store the date as long as the viewDidLoad is not called.
If you are lazy or you just don’t want to change all your code you can do simple trick forcing view to load by putting this line:
So the final code will looks like that:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
This should fix all the issues related above :) hope some of you will find this helpfull. If you want to test this by yourself, here is the link to source code
Keep in mind this is not an elegant solution, it is more like a temporary workaround for the issue. If you cannot rewrite your segues to
UIPopoverPresentationController it is a good idea to put popover loading back to code or use some additional variables in contentViewController to keep your code clean. We can always wait until Apple will put some fix for that.
Ok that’s all for today, next time another funny iOS8 problem i encounter during my regular day work.