有同样的问题，因为我正在使用performSelectorInBackground。

You already have the correct code answer from @Mark but, just to share my findings: The issue is that you are requesting a change in the view and assuming that it will happen instantly. In reality, the loading of a view depends on the available resources. If everything loads quickly enough and there are no delays then you don't notice anything. In scenarios, where there is any delay due to the process thread being busy etc, the application runs into a situation where it is supposed to display something even though its not ready yet. Hence, it is advisable to dispatch these requests in a asynchronous queues so, they get executed based on the load.

我在使用TouchID时遇到了这个问题，如果这对其他人有帮助，包装你的成功逻辑，它可能在主队列中对UI有作用。

如果要查找此错误，请使用主线程检查器暂停问题复选框。 在大多数情况下，修复它很容易，只需将有问题的行分派到主队列中即可。

当您尝试更新文本字段值或在后台线程中添加子视图时，可能会遇到此问题。因此，应该将这类代码放在主线程中。

您需要用dispatch_asynch包装调用UI更新的方法以获得主队列。例如:

dispatch_async(dispatch_get_main_queue(), { () -> Void in
   self.friendLabel.text = "You are following \(friendCount) accounts"
})

编辑- swift 3:

现在，我们可以按照下面的代码来做:

// Move to a background thread to do some long running work
DispatchQueue.global(qos: .userInitiated).async {
   // Do long running task here
   // Bounce back to the main thread to update the UI
   DispatchQueue.main.async {
      self.friendLabel.text = "You are following \(friendCount) accounts"
   }
}

它可以像设置文本字段/标签值或在后台线程中添加子视图一样简单，这可能会导致字段的布局发生变化。确保你对接口所做的任何事情都只发生在主线程中。

查看这个链接:https://forums.developer.apple.com/thread/7399