Update
It has been mentioned that viewWillAppear and viewDidAppear do not get called per the docs. However, I perform no initialization within these methods and no adding UI elements to the view.
I was just using them to place break points to try to debug this.
Any other ideas?
Original Question
I'm stumped. I'm refactoring some code and have come across some strange behavior....
I initialize viewController A without a nib and set the view programmatically.
viewDidLoad in controller A gets called.
Inside viewDidLoad of viewController A, I initialize viewController B from a nib.
I add viewControllerB.view as a subview of viewControllerA.view
viewDidload of controller B gets called.
Then it gets weird:
viewWillAppear and viewDidAppear of viewController B never get called.
viewControllerB.view never makes it on screen.
No errors.
Things I checked:
The name of the viewControllerBs Nib is correct.
The view outlet of viewControllerB is connected to a view.
viewControllerB and its view both are non-nil.
And to top it off, everything works great in SDK [redacted] beta 5!
Any ideas? It's got to be something silly..
Don't forget to call
Wherever you redefine it.
The documentation says:
I guess your view is not the root view. You are probably using a UINavigationController so try to implement this method
or this one
and add in your viewDidLoad
(don't forget to add the UINavigationControllerDelegate protocol in your .h file.
To close the matter:
I could never find a solution, but since then SDK 3.0 is the standard and the point has become moot. The code does work correctly in current versions of the SDK.
If the view controller is added to a view hierarchy through code, the view controller will not get
viewWillAppear
(orviewDidAppear
) messages. If you add it yourself you have to send the view controller the message yourself.Try