In my iOS app, my window's rootViewController is a tab bar controller with the a hierarchy like this:
- UITabBarController
- UINavigationController 1
- FirstContentController
- UINavigationController 2
- ...
- UINavigationController 3
- ...
- ...
- UINavigationController 1
When the user taps a certain row on FirstContentController
, an instance of SecondController
will be pushed onto its navigation controller. SecondContentController
sets hidesBottomBarWhenPushed
to YES
in its init
method and sets self.navigationController.toolbarHidden
to NO
in viewWillAppear:
.
In iOS 6, the user would tap the row in FirstController
and SecondController
would get pushed onto the nav controller. Because it has hidesBottomBarWhenPushed
set, it would hide the tab bar and, by the time the transition animation was complete, SecondController
would be on the screen with its toolbar visible.
However, when testing this under iOS 7, hidesBottomBarWhenPushed
's behavior seems to have changed. What I see now is:
- the tab bar hides, as expected
- the toolbar appears, as expected
- a gap of unusable space exactly 49 pixels tall (the height of the tab bar) appears between the toolbar and the content view
The gap is completely unusable - it doesn't respond to touches and if i set clipsToBounds
to YES on the main view, nothing draws there. After a lot of debugging and examining subview hierarchies, it looks like iOS's autosizing mechanism resizes the view controller's view to a height of 411 (on the iPhone 5). It should be 460 to reach all the way down to the toolbar, but the layout system seems to be including a "ghost" 49-pixel-tall tab bar.
This problem only occurs if the view controller has a tab bar controller as one if its parent containers.
On iOS 7, how can I have the tab bar disappear and a toolbar seamlessly slide into place when a new controller is pushed, and still have the view take up the entire space between the navigation item and the toolbar?
UPDATE
After further investigation, this only happens if SecondController's edgesForExtendedLayout
is set to UIRectEdgeNone
. However, unless I set that property to UIRectEdgeNone
, the view's frame is too long and extends under the toolbar, where it can't be seen or interacted with.
I built a new project using your Gist, and I encased the UITabBarController in a UINavigationController:
And to show the SecondViewController, here is what I did:
Finally, in the secondViewController:
Here's what it does look:
EDIT: Changed the example and changed the screenshot. Made the example iOS6 compatible.
Uncheck "Hide bottoms bars on push" and set your autoconstraints as if there is a tab bar. Then in "ViewDidLoad" of the controller you want to hide the system tab bar, put the following code.
This makes sure the tab bar still accepts user interaction yet not visible to users. (other alternatives such as setting it 0 alpha or hidden will render tab bar useless) Now the autoconstaraints will make sure your view displays correctly with the tab bar height as zero.
You mention that you can fix this by not touching the
edgesForExtendedLayout
. Is there a necessary reason that the content/controls of the view controller are contained in the root view of the pushed view controller? You might consider wrapping everything in a view that is the first and only child of the main view. Then adjust that view's frame in theviewDidLayoutSubviews
of the pushed view controller to avoid having content permanently beneath the toolbar using the top/bottomLayoutGuide of the view controller.I think you can set SecondController's edgesForExtendedLayout to UIRectEdgeBottom.
It's a bug in iOS 7 UIKit due to this particular combination of:
You should file a bug with Apple and include your sample code.
To work around the bug you need to remove one of those four conditions. Two likely options:
Fix the layout of your "second" view controller so that it works correctly when
edgesForExtendedLayout
is set toUIRectEdgeAll
. This could be as simple as setting thecontentInset
on a scroll view.Don't use UINavigationController's built-in toolbar. Instead, create a separate UIToolBar instance and manually add it to your second view controller's view.
The key to this conundrum is that the navigationcontroller.view.frame size doesn't change. Going of batkin's Gist here is a gist of my own.
FirstViewController.m
SecondViewController.m