different addSubview behavior between iOS 4.3 and 5.0(viewWillAppear 不被调用)

最新推荐文章于 2025-04-10 15:43:03 发布

logcabin

最新推荐文章于 2025-04-10 15:43:03 发布

阅读量1.5k

点赞数

分类专栏： iOS 文章标签： ios behavior ios5 uinavigationcontroller uiview apple

iOS 专栏收录该内容

148 篇文章

订阅专栏

这篇文章说的很细：

http://stackoverflow.com/questions/7830830/ios-different-addsubview-behavior-between-ios-4-3-and-5-0

21 down vote favorite

while coding in iOS 4.3 before, I found while add a view controller's view to another view with [superview addSubView:controller.view], the controller instance will not receive the -viewWillAppear/viewDidAppear message, than I found same issue in some thread in stack overflow. After that, I manually call -viewWillAppear/-viewDidAppear as needed.

but, after upgrade to iOS 5.0, some frisky UIView behavior happened. Finally I found that in iOS 5, the [superview addSubView:controller.view] , will send a -viewWillAppear/-viewDidAppear message to the controller instance automatically, plus my manually calls, there are two duplicated message each time the controller action its behavior.

and I also found a similar issue: iOS 5 : -viewWillAppear is not called after dismissing the modal in iPad

Now, the problem is, after search apple's documents, I didn't find any explicitly doc for diff about these issues. I even wonder if this is a guaranteed view life cycle behavior in iOS 5.0 .

Does anyone fix similar issues or find some guidelines about these difference. cause I want to run my app both in 4.x & 5.x iOS.

edited Jan 26 at 13:01

Hot Licks
10.2k 2 7 35

asked Oct 20 '11 at 3:31

KrzyCube
113 1 6

As you've discovered, only about 10% of the changes between iOS 4 and iOS 5 were explicitly documented. – Hot Licks Jan 26 at 13:04

feedback

6 Answers

active oldest votes

up vote 18 down vote accepted

In iOS 4 you had to manually call -viewWillAppear, -viewWillDisappear, etc. when adding or removing a view from your view hierarchy. These are called automatically in iOS 5 if the view is being added or removed from the window hierarchy. Fortunately, iOS 5 has a method in UIViewController that you can override to revert the behaviour back to how it worked with iOS 4. Just add this to your UIViewController:

-(BOOL)automaticallyForwardAppearanceAndRotationMethodsToChildViewControllers {
   return NO;
}

This is probably the easiest solution as long as you're supporting both iOS 4 and iOS 5. Once you drop support for iOS 4 you might consider modifying your code to use the newer approach when swapping views.

Edit 5 February 2012

Apparently this function requires the child view controller be added to the main view controller using the addChildViewController: method. This method doesn't exist in iOS4, so you need to do something like this:

  if ([self respondsToSelector:@selector(addChildViewController:)] ) {
     [self addChildViewController:childViewController];
  }

Thanks to everyone who corrected me on this.

edited Feb 5 at 5:50

answered Nov 9 '11 at 6:40

chris
2,027 2 12 20

Thanks a lot friend!!!! – Neel Nov 10 '11 at 17:56

Thanks, fixed the problem on ios4 but on ios5 viewWillAppear is called twice (one from the manual call I put in) not sure why. – richy Dec 1 '11 at 5:33

Richy.. That's strange since this method is ignored in iOS4 and only called in iOS5. You might want to double check your results. – chris Dec 1 '11 at 7:17

thank you so much! :) – Mayur Birari Jan 17 at 6:04

whalec: I'm not sure I agree with your edits, so probably best to leave your own answer to the original question. – chris Jan 26 at 12:56

show 1 more comment

feedback

up vote 7 down vote

This may not be an answer what you want, but I had same kind of problem.

In my case, when I added a view controller's view to another view controller's view as a subview, the subview was received viewWillAppear only in iOS 5.0 not iOS 4.X.

So I added a nasty condition.

[self.view addSubview:self.viewController.view];
if ([[[UIDevice currentDevice] systemVersion] compare:@"5.0"] == NSOrderedAscending) {
    [self.viewController viewWillAppear:animated];
}

From iOS 5.0, Apple provides a way to implement custom container view controllers like UINavigationController or UITabController. I think this change affects when viewWillAppear is called.

This problem may be solvable if we use -[UIViewController addChildViewController:].

answered Oct 21 '11 at 0:40

hiroshi
611 5 10

	I dont think it has anything to do with OS version. The API remains the same. There are fixed rules as to when viewWillApear/Disappear will get called. stackoverflow.com/questions/131062/… – debuggerman Oct 25 '11 at 13:02
	thanks lot for your help! :) – Mayur Birari Jan 17 at 6:11

feedback

up vote 4 down vote

The answers above a slightly incomplete.Let's presume you have 2 view controllers, ControllerA, and ControllerB.

ControllerA.view is already added to the window(it is the parent), and you want to add ControllerB.view as a subview of ControllerA.

If you do not add ControllerB as a child of ControllerA first, the automaticallyForwardAppearanceAndRotationMethodsToChildViewControllers will be ignored, and you will still be called by iOS5, meaning that you'll call your view controller callbacks twice.

Example in ControllerA:

- (BOOL)automaticallyForwardAppearanceAndRotationMethodsToChildViewControllers {
    return NO;
}

- (void)viewDidLoad
{
    [super viewDidLoad];
    self.controllerB = [[ControllerB alloc] initWithNibName:@"ControllerB" bundle:nil];

    [self.view addSubview:self.controllerB.view];
}

- (void)viewWillAppear:(BOOL)animated
{
    [super viewWillAppear:animated];
    [self.controllerB viewWillAppear:animated];
}

In ControllerB NSLogging in viewWillAppear:

- (void)viewWillAppear:(BOOL)animated
{
    NSLog("@ControllerB will appear");
}

This will result in iOS5 only displaying that NSLog message twice. i.e. You're automaticallyForwardAppearanceAndRotationMethodsToChildViewControllers has been ignored.

In order to fix this, you need to add controllerB as a child of controller a.

Back in ControllerA's class:

- (void)viewDidLoad
{
    [super viewDidLoad];
    self.controllerB = [[ControllerB alloc] initWithNibName:@"ControllerB" bundle:nil];
    if ([self respondsToSelector:@selector(addChildViewController:)])
        [self addChildViewController:self.controllerB];

    [self.view addSubview:self.controllerB.view];
}

This will now work as expected in both iOS4 and iOS5 without resorting to the horrible hack of checking iOS version strings, but instead checking on if the function we're after is available.

Hope this helps.

answered Jan 27 at 4:50

whalec
43 3

feedback

up vote 1 down vote

It is iOS5 behavior:
viewWillAppear, viewDidAppear, ... are executed automatically after addSubView: for iOS5.
So for iOS5 no need to execute manually those methods as need for iOS<5.0.

The fix may be:

if ([[UIDevice currentDevice].systemVersion doubleValue] < 5.0) {
...execute viewWillAppear or other
}

answered Oct 25 '11 at 12:45

Alex Sfinx87
51 7

feedback

up vote 0 down vote

By this method u know which os u use and put condition if is less then 5.0 or other one

[[UIDevice currentDevice] systemVersion]