Unbalanced Calls to Begin/End Appearance Transitions for <Uitabbarcontroller: 0X197870>

Unbalanced calls to begin/end appearance transitions for UITabBarController: 0x197870

Without seeing more of the surrounding code I can't give a definite answer, but I have two theories.

1. You're not using UIViewController's designated initializer initWithNibName:bundle:. Try using it instead of just init.

2. Also, self may be one of the tab bar controller's view controllers. Always present view controllers from the topmost view controller, which means in this case ask the tab bar controller to present the overlay view controller on behalf of the view controller. You can still keep any callback delegates to the real view controller, but you must have the tab bar controller present and dismiss.

Unbalanced calls to begin/end appearance transitions for FirstViewController: 0x2a2c00

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.

Unbalanced calls to begin/end appearance transitions for DetailViewController when pushing more than one detail view controller

"The unbalanced calls to begin/end appearance transitions"

occurs when you try and display a new viewcontroller before the current view controller is finished displaying. You can reproduce it by navigating in viewWillAppear.

Basically you are trying to push two view controllers onto the stack at almost the same time. Suggest you maintain a queue in the tableview controller which maintains a list of the detail views which need displaying. Push one at a time on to the stack and check on exit from the current detail view whether there are any queued detail views which need displaying.

This kind of navigation is going to be confusing for the user. It may be better to consider making your detail view support multiple items.

Unbalanced calls to begin/end appearance transitions for UITabBarController

You need to wait to present the modal view controller until the next run loop. I ended up using a block (to make things more simple) to schedule the presentation for the next run loop:

Update:

As mentioned by Mark Amery below, just a simple dispatch_async works, there's no need for a timer:

dispatch_async(dispatch_get_main_queue(), ^(void){     
  [self.container presentModalViewController:nc animated:YES]; 
});

---

/* Present next run loop. Prevents "unbalanced VC display" warnings. */
double delayInSeconds = 0.1;
dispatch_time_t popTime = dispatch_time(DISPATCH_TIME_NOW, delayInSeconds * NSEC_PER_SEC);
dispatch_after(popTime, dispatch_get_main_queue(), ^(void){
    [self.container presentModalViewController:nc animated:YES];
});

Swift Unbalanced calls to begin/end appearance transitions for

This issue occurs if you trying to push new view controller while previous transaction (animation) in progress. So please check your code flow and make the appropriate changes. Check your dismiss and present view animations. You can use property setAnimation to 'YES/NO'resolve this

Set animated:NO, may be solve your problem

Container View Controller - Unbalanced calls to begin/end appearance transitions

I had a similar issue. Generally, that warning appears when you try to present the same view controller without dismissing it first, but the transition method should handle all that for you. I ended up fixing it by using

UIView.animate(withDuration:animations:completion:)

instead of

UIViewController.transition(from:to:duration:options:animations:completion:)

as you are above. Of course, I had to manually add and remove the subviews as well. I'm not sure why this change worked, but my best guess is that there's something wrong with the UIViewController transition method that issues that warning. Fortunately the fix is really easy.

Keep getting Unbalanced calls to begin/end appearance transitions for ViewController error

I found the answer this morning in another stackoverflow question. The answer can be found here.

When I had originally setup the Push Segue, I clicked on and dragged from a button, and was also calling the performSegueWIthIdentifier method inside that button's IBAction method implementation. This was causing 2 identical push segues to be executed on the button press. I just left my method call in the IBAction, deleted the old push segue, and created a new push segue only this time I clicked on and dragged from the entire View Controller instead of it's button.

Unbalanced calls to begin/end appearance transitions with custom segue

Looks like this behaviour is the result of some - as of yet - undocumented change in recent iOS releases.
Getting frustrated with your exact issue and the lack of satisfying answers I've come up with this:

// create a UIImageView containing a UIImage of `view`'s contents
func createMockView(view: UIView) -> UIImageView {
    UIGraphicsBeginImageContextWithOptions(view.frame.size, true, UIScreen.mainScreen().scale)

    view.drawViewHierarchyInRect(view.bounds, afterScreenUpdates: true)
    let image = UIGraphicsGetImageFromCurrentImageContext()

    UIGraphicsEndImageContext()
    return UIImageView(image: image)
}

override func perform() {

   let src:UIViewController = self.sourceViewController as! UIViewController
   let dstn:UIViewController = self.destinationViewController as! UIViewController
   let mock = createMockView(dstn.view)

   src.view.addSubview(mock)
   mock.alpha = 0

   UIView.animateWithDuration(0.75, delay: 0.1, options: UIViewAnimationOptions.TransitionCrossDissolve, 
     animations: { () -> Void in
        mock.alpha = 1
     },
     completion: { (finished) -> Void in
        src.presentViewController(dstn, animated: false, completion: { mock.removeFromSuperView()})
   })
}

createMockView() will create a UIImageView containing a snapshot of the destination VCs contents and use that to do the transition animation.
Once the transition is finished the real destination VC is presented without animation causing a seamless transition between both. Finally once the presentation is done the mock view is removed.

---

Related Topics