Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Status bar is Landscape, but [[UIApplication sharedApplication] statusBarOrientation] returns portrait

This problem appears to be intermittent, but I am not sure why exactly. When running my application on the device (iPad), I have some code to load a scroll view with some image views according to the current device orientation. Even though the device is landscape before loading, the views are being loaded as if it were portrait.

The orientation is found by calling [[UIApplication sharedApplication] statusBarOrientation].

The views are set up to adjust their positions when the device is rotated, and indeed, rotating to portrait and then back to landscape returns them to the correct landscape positions. Is it the case that all applications start off in portrait and soon change to landscape if required? Am I trying to check the orientation too soon (during the init of the first view controller to be loaded)?

like image 716
Stuart Avatar asked Apr 27 '11 20:04

Stuart


2 Answers

OK Fixed.

Using UINavigationController, when I popToViewController:animated: from a landscape view to a portrait view, the destination view appears correct but the status bar and also the UIKeyboard keeps the landscape configuration, making a real mess.

Working around After thousands of recommendations about statusBarOrientation and references read... https://developer.apple.com/library/content/releasenotes/General/RN-iOSSDK-6_0/index.html

"The setStatusBarOrientation:animated: method is not deprecated outright. It now works only if the supportedInterfaceOrientations method of the top-most full-screen view controller returns 0. This makes the caller responsible for ensuring that the status bar orientation is consistent." (thanks to Vytis in here)

statusBarOrientation only works if supportedInterfaceOrientations returns 0, so... that give us a guess.

If statusBarOrientation is not as expected, one zero return will do it (if always return 0, the view wont rotate, so:

// if deviceOrientation is A (so I expect statusbarOrientation A
// but statusbarOrientation is B
// return 0
// otherwise 
// return user interface orientation for A

- (NSUInteger)supportedInterfaceOrientations {
    UIDeviceOrientation deviceOrientation = [[UIDevice currentDevice] orientation];
    UIInterfaceOrientation statusBarOrientation =[UIApplication sharedApplication].statusBarOrientation;
    if(deviceOrientation == UIDeviceOrientationPortrait || deviceOrientation == UIDeviceOrientationPortraitUpsideDown){
        if(statusBarOrientation != UIInterfaceOrientationPortrait ||statusBarOrientation != UIInterfaceOrientationPortraitUpsideDown){
             return 0;
        }
    }
    // otherwise
    return UIInterfaceOrientationMaskPortrait;
}

Now, in viewDidAppear (believe me, I use this call even when the keyboard notification is recived:

[UIApplication sharedApplication].statusBarOrientation = UIInterfaceOrientationPortrait;

more than 48 labor hrs in this. Hope this helps a while, thanks to all.

like image 120
CesareoAguirre Avatar answered Oct 07 '22 08:10

CesareoAguirre


If you're subclassing UIWindow or the status bar you'll see this because that's the ipad device's native orientation. The UIWindow translates the orientation and coordinates into what we're used to. After you makeAndKeyVisible, your device and interface orientation in view controllers should be as expected. You wouldn't by chance be using MTStatusBarOverlay would you? I went through the same thing and it came down to the order of instatiation.

like image 35
Greg Combs Avatar answered Oct 07 '22 07:10

Greg Combs