Ios – nested push animation can result in corrupted navigation bar

iosipadiphoneobjective c

in one of my viewcontroller, lets say A, I have the following:

 OnbViewController *on = [[OnbViewController alloc] initWithNibName:nibName bundle:nil];
        onboardingTutorial.delegate_ = self;
self.test = on
 UINavigationController *nController = [[UINavigationController alloc] initWithRootViewController:self.test]
[self presentModalViewController:nController]
[nController release];

then inside OnbViewController I have pushed to the navigationController:

[self.navigationController pushViewController:someViewController];

then in didSelectRowForIndexPath: I called a delegate, which is A, inside the delegate function I called I tried to push again by doing:

[self.test pushViewController:someOtherViewController];

and then this gives me that error:

nested push animation can result in corrupted navigation bar
Finishing up a navigation transition in an unexpected state. Navigation Bar subview tree might get corrupted.
   Unbalanced calls to begin/end appearance transitions for <someOtherViewController: 0x6f942e0>.

any idea?

Best Answer

Rather convoluted calling sequence, but the first issue I see is that it looks like you're calling pushViewController on an OnbViewController, not on its navigationController. Maybe changing to [self.test.navigationController pushViewController:someOtherViewController]; will suffice?

Edit: in looking further at this, I note the "animation" in "nested push animation". Is onbViewController pushing to someViewController during its viewWillAppear or somewhere early like that? Maybe skipping the second animation will work?

Related Solutions

Ios – nested push animation can result in corrupted navigation bar PUSH POP PUSH

The problem is you are calling pop and push with animation back to back. In iOS6 the push call is basically ignored but in iOS7 the push is called while the pop is being animated hence they are "nested" and you get the following:

nested push animation can result in corrupted navigation bar show

Instead of popping inside doneSucceed you can make the pop call from the SecondViewController. Then wait for the FirstViewController's viewDidAppear to push the ThirdViewController. You can use the doneSucceed method as a way toggle whether or not you should transition to the ThirdViewController on viewDidAppear

IOS: nested push animation can result in corrupted navigation bar

You may have a Segue in the Storyboard which triggers when a table row is selected. When you also manually push a controller when a row is selected the error which you describe occurs. You should remove the segue from the storyboard.

EDIT: More details:

I assume you use a storyboard (more than one view controller in the design window). If you do not use it, I am on the wrong track. For example take this screenshot from one of my projects:

Storyboard screenshot

If you have control-dragged from the "Row" to the view controller on the right, you created a segue. It is likely that this segue is triggered when you select a row in the tableview in the left view controller. If you used a standard project, such a segue may already exist and you did not create it yourself.

The segue fires "automatically" when you select a row. When you manually push view controllers in code, you may cause a "second push" which disturbs the navigation controller.

You could just delete the segue by clicking on the thick line between the scenes or on that round icon and press delete.

If you need a segue which does not automatically trigger when a row is selected, you can control-drag it from that yellow icon to the target scene. A menu should appear and you would choose one of the options under "manual". Then the segue must be triggered manually which you would do in code with:

[self performSegueWithIdentifier:@"SegueId" sender:self];

When you click on the round segue icon in the storyboard, you can set an identifier in the utilities window in the attributes inspector in the field "Identifier". That identifier is the string used in the code line above.

Related Topic