Unknown error [UIWindow endDisablingInterfaceAutorotation]

Question

I get this error. I have no idea why this will be caused, and Google really didn't help. Any suggestions?

-[UIWindow endDisablingInterfaceAutorotation] called on <UIWindow: 0x4e0ec50; frame = (0 0; 320 480); opaque = NO; autoresize = RM+BM; layer = <CALayer: 0x4e0f9e0>> without matching -beginDisablingInterfaceAutorotation. Ignoring. 

Answer 1

It looks like you need to call -beginDisablingInterfaceAutorotation first, and you will not.

Answer 2

I had the same issue recently. It turned out that I accidentally showed the same UIActionSheet twice. eg.

 [actionSheet showInView:aView]; ... more code ... // WOOPS! I already did this [actionSheet showInView:aView]; 

When the UIActionSheet is rejected (about the 12th time, possibly -beginDisablingInterfaceAutorotation stack depth), it caused an error. Removing redundant call in -showInView: fixed problem.

Answer 3

I had a similar problem when doing a custom presentation of a UIViewController using the UIViewControllerAnimatedTransitioning class. For me, the printouts looked like this:

 -[UIApplication endIgnoringInteractionEvents] called without matching -beginIgnoringInteractionEvents. Ignoring. -[UIWindow endDisablingInterfaceAutorotationAnimated:] called on <UIWindow: 0x7f9f83f42db0; frame = (0 0; 375 667); autoresize = W+H; gestureRecognizers = <NSArray: 0x7f9f83f44ed0>; layer = <UIWindowLayer: 0x7f9f83f40ca0>> without matching -beginDisablingInterfaceAutorotation. Ignoring. -[UIWindow endDisablingInterfaceAutorotationAnimated:] called on <UITextEffectsWindow: 0x7f9f862553a0; frame = (0 0; 375 667); opaque = NO; autoresize = W+H; layer = <UIWindowLayer: 0x7f9f83f9a1e0>> without matching -beginDisablingInterfaceAutorotation. Ignoring. 

I found out that the error was caused by calling transitionContext.completeTransition(true) twice (once in animateTransition(_:) and the other in the CAAnimation delegate animationDidStop(_:flag:) method). You might want to check that you are not doing something like that.

Answer 4

Adding UIViewAnimationOptionLayoutSubviews to the animation options solved my problem.

Answer 5

I ran into a similar problem for no reason. In my assembly, nothing has changed. All I had to do was remove my application from my testing device, rebuild and reinstall, and this problem was resolved. Worth taking a picture!