我发现故事板中的segue有点坏了。删除segue(并再次创建完全相同的segue)解决了这个问题。

我通过将start()函数移动到解散完成块内部来修复它:

self.tabBarController.dismiss(animated: false) {
  self.start()
}

Start包含对self.present()的两个调用，一个用于UINavigationController，另一个用于UIImagePickerController。

这为我解决了问题。

当我试图在viewDidLoad中呈现一个UIViewController时，我也遇到了这个问题。James Bedford的答案是可行的，但我的应用程序先显示了1到2秒的背景。

经过一些研究，我找到了一种方法来解决这个使用addChildViewController。

- (void)viewDidLoad
{
    ...
    [self.view addSubview: navigationViewController.view];
    [self addChildViewController: navigationViewController];
    ...
}

我的问题是，在我调用窗口上的makeKeyAndVisible()之前，我在UIApplicationDelegate的didFinishLaunchingWithOptions方法中执行segue。

In case it helps anyone, my issue was extremely silly. Totally my fault of course. A notification was triggering a method that was calling the modal. But I wasn't removing the notification correctly, so at some point, I would have more than one notification, so the modal would get called multiple times. Of course, after you call the modal once, the viewcontroller that calls it it's not longer in the view hierarchy, that's why we see this issue. My situation caused a bunch of other issue too, as you would expect.

总之，无论你做什么，都要确保模态不会被调用超过一次。

我已经结束了这样一个代码，最终工作给我(Swift)，考虑到你想要显示一些viewController从几乎任何地方。当没有可用的rootViewController时，这段代码显然会崩溃，这是开放式结局。它也不包括通常需要切换到UI线程使用

dispatch_sync(dispatch_get_main_queue(), {
    guard !NSBundle.mainBundle().bundlePath.hasSuffix(".appex") else {
       return; // skip operation when embedded to App Extension
    }

    if let delegate = UIApplication.sharedApplication().delegate {
        delegate.window!!.rootViewController?.presentViewController(viewController, animated: true, completion: { () -> Void in
            // optional completion code
        })
    }
}