解散ModalViewControllerAnimated:(和dismissViewControllerAnimated)在iOS 5中崩溃 [英] dismissModalViewControllerAnimated: (and dismissViewControllerAnimated) crashing in iOS 5

问题描述

我找不到任何合乎逻辑的解释，但事实仍然是，在 iOS 5 (xCode 4.2) 中，如果我presentModalView:* animation:YES，我可以调用dismissModalViewAnimated:* 很好，但是如果我调用presentModalView:*动画:否，然后调用dismiss方法崩溃.(如果我使用新的presentViewController:animated:completion:+dismissViewControllerAnimated:，这也是一样的).我现在要尝试解决这个问题(我不希望演示文稿动画化)并向 Apple 报告一个错误，但我一直在努力解决这个问题.欢迎任何和所有建议.iOS 5 上的内容不多，所以如果可以，请提供帮助.在 iOS 4 或 iOS 5 中不会崩溃的示例代码:

I can't find any logical explanation, but the fact remains that, in iOS 5 (xCode 4.2), if I presentModalView:* animated:YES, I can call dismissModalViewAnimated:* fine, but if I call presentModalView:* animated:NO, then calling the dismiss method crashes. (This works the same if I use the new presentViewController:animated:completion: + dismissViewControllerAnimated:). I am going TRY to work around this for now (I don't want the presentation animated) and report a bug to Apple, but I have been beating my head on this for a while. Any and all suggestions are welcome. Not much out there on iOS 5, so please help if you can. Sample code that does not crash in iOS 4 or iOS 5:

LoginController *loginController = [[LoginController alloc] initWithNibName:@"LoginControllerGG" bundle:nil];
[self presentModalViewController:loginController animated:YES];
[loginController release];
...
[self dismissModalViewControllerAnimated:YES];

这将在 iOS 5 中崩溃并在关闭调用中使用 EXC_BAD_ACCESS:

This will crash in iOS 5 with EXC_BAD_ACCESS on the dismiss call:

LoginController *loginController = [[LoginController alloc]    initWithNibName:@"LoginControllerGG" bundle:nil];
[self presentModalViewController:loginController animated:NO];
[loginController release];
...
[self dismissModalViewControllerAnimated:YES]; //crashes with EXC_BAD _ACCESS

一个注意事项:我在 loginController 中有一个在 viewDidLoad 上发生的动画.想看看去掉它是否会改变任何东西，但我想把它拿出来，因为我需要尽快找到解决方案.

One note: I have an animation within the loginController that happens on viewDidLoad. Going to see if taking that out changes anything, but I wanted to get this out there since I need a solution asap.

完整代码流...在 AppDelegate 中，application:didFinishLaunchingWithOptions:

Full code flow... In AppDelegate, application:didFinishLaunchingWithOptions:

if (!loggedIn)  [myViewController showLoginPanel];

在我的视图控制器中:

- (void)showLoginPanel {    
    LoginController *loginController = [[LoginController alloc] initWithNibName:@"LoginControllerGG" bundle:nil];
    if ([self respondsToSelector:@selector(presentViewController:animated:completion:)]) {
        [self presentViewController:loginController animated:NO completion:nil];
    } else {
        [self presentModalViewController:loginController animated:NO]; //iOS 4 works fine with or without animation   
    } 
    [loginController release];  
}

在登录控制器中:

- (IBAction)closeLoginWindow {
    [[NSNotificationCenter defaultCenter] postNotificationName:@"CloseLoginWindow" object:nil];
}   //doing it this way because calling on the self.parentViewController doesn't work

回到 myViewController:

Back in myViewController:

- (void) viewDidLoad
    ...
[[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(closeLoginWindow) name:@"CloseLoginWindow" object:nil];
    ...

- (void)closeLoginWindow {
    if ([self respondsToSelector:@selector(dismissViewControllerAnimated:completion:)]) {
        [self dismissViewControllerAnimated:YES completion:nil];    //iOS 5 crashes only if presentation was not animated
    } else [self dismissModalViewControllerAnimated:YES];    //deleting the previous condition, iOS 5 still crashes if presentation was not animated
}    

推荐答案

在 iOS5 中生命周期的管理不知何故发生了变化，我无法详细解释这个问题.无论如何，解决方法是将该工作流从 applicationDidFinishLaunchingWithOptions 推迟到 applicationDidBecomeActive.似乎有些东西没有在 applicationDidFinishLaunchingWithOptions 的调用中初始化.

In iOS5 the managing of the lifecyle somehow changed and I cannot explain that issue in detail. Anyway, the fix is to postpone that workflow from applicationDidFinishLaunchingWithOptions to applicationDidBecomeActive. It seems that something isn't initialized right at the call of applicationDidFinishLaunchingWithOptions.

- (void)applicationDidFinishLaunchingWithOptions:... {    
    // in order to do this only at launching, but not on every activation 
    // Declaration as property for example
    applicationDidLaunch = YES;
}

- (void) applicationDidBecomeActive:(UIApplication *)application {
    if (applicationDidLaunch) {
        applicationDidLaunch = NO;
        [Start your login Workflow with modal view presenting here]
    }
}

对你的反馈感到好奇:)....

Curious to ur feedback :)....

这篇关于解散ModalViewControllerAnimated:(和dismissViewControllerAnimated)在iOS 5中崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！