Here is the screen where the grey area is shown between navigation bar and video player .
I read this one as well.
Grey bar appearing under Navigation bar after segues Swift
But didn't understood the solution as it didn't worked for me.
Need help to get this portion off.
Anyone faced this?
Thanks in advance
I have used MFSideMenu in objectiveC. But when the sideMenu appear the black background show on top.
I have use all (header and footer of tableview). Also hide the Navigation Bar.But problem is not solve.
Can Anybody help me.
I know this question has been asked before. I have already tried this Navigation Bar not showing in Storyboard. I have a navigation bar and a toolbar. They were showing in the storyboard fine before I restarted my system. They work completely fine during runtime but I am no longer able to access it using Storyboard. I have also tried changing top bar for Simulated metrics. Here is the screenshot for the same.
Make sure it is ticked here for Navigation Controller in Storyboard:
Try This seems like your frame is misplaced from the top and not according to the constraint too
I am currently working on a basic app that has many single view view controllers. I am trying to add a navigation bar to one of my view controllers, when using the "Suggested Constraints", I can see nothing. When the only restraint on the Navigation bar is a center horizontal, it shows up but I think it is too long for the screen. When I tried to add a button on the left side of the Navigation bar, it would not show up in my app because the navigation bar does not have the correct width. I know I have the wrong constraint setup, please help.
I have a strange one that I can not seem to fix. I am currently working on updating my app to iOS7. This all worked in iOS6. It is an universal app and thus uses same xib files. However the iPad uses UISplitViews on some. Like I said, this all worked in iOS6 oh this all works on the iPhone too.
The problem is a grey bar at the bottom. I changed the tab bar to be opaque to move views up properly as i had some UI clipped to bottom of views and that went underneath the tab bar, sidetracked there. But if i set it back to translucent bar, it goes underneath but stretched properly. if i dont, it adds a bar. Other tabs work fine when NOT using splitview.
The UISplitviewController is added programmatically.
See attached image for better description.
This I have tried:
Added autoresize on splitview
Checked xib for subviews in the splitviews to have auto resize
Tried to force splitview to be screen bounds
Removed clips to bounds on all views
Removed autoresize subviews
Any ideas would be welcomed.
Thank you all.
UPDATE:
setting the background colour the uisplitview, it does colour the bar black. So the uisplitview is definitely stretching to it.
I subclassed UISplitViewController and added the line below to viewDidLoad and that fixed the grey line.
self.extendedLayoutIncludesOpaqueBars = YES;
I believe I have found an alternative solution for you. I have had the exact same problem, mostly because we are both doing something against Apple's Guidelines which is having a SplitViewController nested within a Tabbar controller (SplitView should be the root view). This was okay in iOS 5/6, but now in iOS 7 there are far too many side effects to achieve this.
The reason you see your view stretch completely when you set the bar to be translucent is because the bar is NOT taken into account when drawing the view. When you set translucent to false, it is then taken into account of the view and you will see that grey bar there because that's your view pretending there's a tabbar at the bottom of the screen.
And as always, a SplitViewcontroller's height cannot be changed, as it is determined by the visible window height.
I tried everything you did and then some. The real solution came from using a third-party Split View Controller.
I recommend switching over to https://github.com/mattgemmell/MGSplitViewController . This split view controller is actually one large View with container views living inside of it. Because of this, you avoid all the side effects of putting an actual split view controller within a tab bar.
If that doesn't float your boat, you could create your own solution which follows the same idea of having one UIViewController with two container views contained in it, though the people behind MGSplitViewController did a good job of that already.
This was the only way I was able to solve this issue, let me know if you find an alternative.
Instead of creating a subclass for UISplitViewController, I just added this code on my master's viewDidLoad:
self.splitViewController?.extendedLayoutIncludesOpaqueBars = true
For the controller that is the detail view of UISplitViewController you just do this:
-(UITabBarController*)tabBarController{
return nil;
}