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

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

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

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

您需要用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"
   }
}

对我来说，问题是这样的。 确保在主线程上执行performSegueWithIdentifier::

dispatch_async (dispatch_get_main_queue(), ^{
  [self performSegueWithIdentifier:@"ViewController" sender:nil];
});

I also encountered this problem, seeing a ton of these messages and stack traces being printed in the output, when I resized the window to a smaller size than its initial value. Spending a long time figuring out the problem, I thought I'd share the rather simple solution. I had once enabled Can Draw Concurrently on an NSTextView through IB. That tells AppKit that it can call the view's draw(_:) method from another thread. After disabling it, I no longer got any error messages. I didn't experience any problems before updating to macOS 10.14 Beta, but at the same time, I also started modifying the code to perform work with the text view.

它需要放在一个不同的线程中，允许UI在线程函数执行完成后立即更新:

现代迅速:

DispatchQueue.main.async {
    // Update UI
}

旧版本的Swift，在Swift 3之前。

dispatch_async(dispatch_get_main_queue(){
    // code here
})

objective - c:

dispatch_async(dispatch_get_main_queue(), ^{
    // code here
});