I have a UIViewController
that I am loading from inside another view controller and then adding its view to a UIScrollView
.
self.statisticsController = [self.storyboard instantiateViewControllerWithIdentifier:@"StatisticsViewController"];
self.statisticsController.match = self.match;
[self.scrollView addSubview:self.statisticsController.view];
I've put breakpoints in the statistics view controller and viewDidLoad
is being called but viewWillAppear
isn't.
Is it because I'm not pushing it onto the hierarchy or something?
As mentioned in another answer, the parent view controller might not call
viewWillAppear
etc. whenshouldAutomaticallyForwardAppearanceMethods
is set tofalse
.UINavigationController
andUITabBarController
are known to do that. In this case, you need to callbeginAppearanceTransition(_ isAppearing: Bool, animated: Bool)
on the child view controller withisAppearing
set totrue
when the view appears and vice versa.You have to place these calls at appropriate places in your code, normally when you add and remove your child view controller.
Don't forget to call
endAppearanceTransition
on your child view controller when your custom transition has ended, otherwiseviewDidAppear
andviewDidDisappear
are not called.You should add
statisticsController
as a child view controller of the controller whose view you're adding it to.I'm not sure this will make
viewDidAppear
get called, but you can overridedidMoveToParentViewController:
in the child controller, and that will be called, so you can put any code that you would have put inviewDidAppear
in there.Per Apple (https://developer.apple.com/library/content/featuredarticles/ViewControllerPGforiPhoneOS/ImplementingaContainerViewController.html), the correct order of API calls to add a child view controller is:
But I still had the problem where viewWillAppear in the child VC was not sporadically getting called. My issue was that there was a race condition that could cause the code above to get executed before viewDidAppear in the container view controller was called. Ensuring that viewDidAppear had already been called (or deferring the addition of the child VC until it was) solved it for me.
The previous answers are correct, but in case it helps someone - if you override
loadView
in the child view controller, then none of the other UIViewController methods get called.Took me some time to realize why my code wasn't running properly, until I realized that I had accidentally overridden
loadView
instead ofviewDidLoad
.By default, appearance callbacks are automatically forwarded to children. It's determined with shouldAutomaticallyForwardAppearanceMethods property. Check value of this propery, if it's NO and if your child viewController should appear right on container's appearance, you should notify child with following methods in container's controller life-cycle implementation:
Customizing Appearance and Rotation Callback Behavior
Fixed my problem! Hope it would be helpful.
I encounter
-viewWillAppear:
not called problem again. After googling, I came here. I did some tests, and find out that the calling order of-addSubview
and-addChildViewController:
is important.Case 1. will trigger
-viewWillAppear:
of controller, but Case 2, it WON'T call-viewWillAppear:
.Case 1:
Case 2: