Question

I’m in the process of migrating an App to the current iOS SDK. Its root controller is UINavigationController with another UINavigationController as first view controller.

The application now crashes with EXC_BAD_ACCESS caused by some kind of infinite recursion, but I can’t make sense of the strack trace. As far as I can tell, nothing has changed expect some project settings to make it compile on the current SDK.

I created a new Navigation-based Application and added a nested UINavigationController, which also crashed the application. Is nesting UINavigationControllers generally a bad idea?

Any hints what might be causing this or how to interpret the stack trace and debug the problem are greatly appreciated.

Answer 1

It will work when you set the navigationbar of the parent navigation controller to hidden (in interface builder or in code) before loading the view:

navigationController.navigationBar.hidden = YES;
[self.window addSubview:navigationController.view];