Unbalanced calls to begin/end appearance transitions for

Question

I have this problem when I simulate my app, its not an error or a warning but it appears in my console, has anyone ever experienced this before?

Answer 1

This was a tough one for me: I've overridden

override func shouldAutomaticallyForwardRotationMethods() -> Bool {
    return true
}

without overriding:

override func shouldAutomaticallyForwardAppearanceMethods() -> Bool {
    return true
}

in my window root navigation controller. then a child navigation controller complained when pushing another view controller with the above mentioned warning. The warning wasn't the worst, the big problem was, that there the delegate of the child navigation controller weren't called anymore. weired.

Answer 2

In my case, this error occurs when you click two tabs in a tableview very fast.

The result causes wrong titlename, back button disappear. Someone mentioned that when you push a view, set animated:NO. The error will disappear but still causes some strange behavior. It pushes two views, then you need to back twice to get back the tableview screen.

Method I tried in order to resolve this problem:

add BOOL cellSelected;

in viewWillAppear cellSelected = YES;

in didselectcell delegate if (cellSelected){cellSelected = NO; do action ; }

This helps prevent clicking two different cells very fast.

Answer 3

In my case it happened when I triggered [self performSegueWithIdentifier:@"SomeIdentifier" sender:self]; within a UINavigationController item's viewDidLoad method.

Moving it into the viewDidAppear method solved the problem.

The reason very likely is that in viewDidLoad not all of the fancy animations have already been finished, whereas in viewDidAppear everything's done.

Answer 4

I also had this problem when I tapped a button from a NIB. It turns out I had accidentally wired the button to send an event to two IBAction methods, each of which did a pushViewController:animated:

Answer 5

Reason For message: This message get displayed if and only if you are pushing/presenting another View controller from viewWillAppear,loadView,init or viewDidLoad method of current View Controller

Way to Remove error Message: Move your pushing/presenting code to viewDidAppear method will solve the issue

Answer 6

You can run into this if you try to dismiss a UIViewController before it is finished loading.

I had this message in the console and was focusing entirely on the UIViewController that was presenting the new UIViewController, without success. I finally discovered the problem was in the UIViewController I was presenting was dismissing itself because the user wasn't logged into their account.

Hope this helps someone.