我相信我找到了一个更通用的解决方案。下面是我用来鼓励Xcode不要产生SourceKitService Terminated错误的步骤。

我的症状是:

When I would start up a new playground, I would receive an error about not being able to communicate with the playground (Error running playground: Failed prepare for communication with playground. See this image on twitter. When I would switch the playground from OS X to iOS, I would receive another error (unfortunately I did not write that one down). When I would start to type in an iOS based Swift project, attempting to use code completion/intellisense on any UIKit specific class, I would receive the SourceKitService Terminated issue in this thread.

调试过程:

我开始通过谷歌寻找SourceKitService，这得到了很少。 然后我开始监视控制台。应用程序，同时使用Xcode。这显示了几个错误: IDEPlaygroundDocument:运行游乐场时遇到错误 com.apple.CoreSimulator。CoreSimulatorService[3952]: The runtime for The selected device is not installed。

我做了什么来纠正这个问题。

如果您只是在Swift项目上下文中遇到问题，请先单独尝试一下。如果这不起作用，那么尝试下面的所有步骤。

打开项目并将目标的部署目标更改为<= 7.1。

更漫长和复杂的过程。 (前3步不一定有帮助，但我做到了，所以把它们记录在这里)

Completely delete all copies of Xcode on your system. Restart your computer. Reinstall Xcode6-beta only. Verify that you still have the issue in playground and/or projects. Open iOS Simulator. Hardware -> Device -> Manage Devices Remove all devices. Recreate all devices you want. I appended the iOS version to the end of the name, just because. Restart Xcode and the simulator. Verify that at least playgrounds no longer throw issues when switched from OS X to iOS. Open your project and change the target's deployment target to something <= 7.1.

分析

看来问题是Xcode6不能正确地找到并连接到模拟器。我不知道为什么会出现这种情况，但这让我可以继续使用Swift进行开发。这可能与模拟器二进制文件似乎移动的事实有关。

报告给苹果公司(#17266321):

细节:

简介: 如果我们试图将值作为数组打印一个字典，则弹出窗口会不断弹出-“SourceKit terminated.”编辑器功能暂时受限”。Xcode冻结并失去上下文识别，导致文本变黑。

复制步骤: 1. 创建一个数组为- "var iOSHistoryArray = ["iOS6"，"iOS7"，"iOS8"，]"

创建一个字典as -"var MacOSYosemiteFeatures: dictionary = ["Device":iOSHistoryArray]"。 将字典打印为- "println("包含数组值的字典:%@ \n"，MacOSYosemiteFeatures)"(< < -罪魁祸首——> >) 第3步导致了注释问题，这使得Xcode再次起作用。

预期结果: Xcode应该能正常工作。

实际结果: Xcode变得无功能，失去上下文识别(所有字体丢失，所有文本变成纯黑色)，整个Xcode变成非活动。

版本: 版本6.0 (6A215l)

我发现，通过显式地(静态地)键入变量类型，而不是推断它们，为我解决了这个问题。

我相信我找到了一个更通用的解决方案。下面是我用来鼓励Xcode不要产生SourceKitService Terminated错误的步骤。

我的症状是:

When I would start up a new playground, I would receive an error about not being able to communicate with the playground (Error running playground: Failed prepare for communication with playground. See this image on twitter. When I would switch the playground from OS X to iOS, I would receive another error (unfortunately I did not write that one down). When I would start to type in an iOS based Swift project, attempting to use code completion/intellisense on any UIKit specific class, I would receive the SourceKitService Terminated issue in this thread.

调试过程:

我开始通过谷歌寻找SourceKitService，这得到了很少。 然后我开始监视控制台。应用程序，同时使用Xcode。这显示了几个错误: IDEPlaygroundDocument:运行游乐场时遇到错误 com.apple.CoreSimulator。CoreSimulatorService[3952]: The runtime for The selected device is not installed。

我做了什么来纠正这个问题。

如果您只是在Swift项目上下文中遇到问题，请先单独尝试一下。如果这不起作用，那么尝试下面的所有步骤。

打开项目并将目标的部署目标更改为<= 7.1。

更漫长和复杂的过程。 (前3步不一定有帮助，但我做到了，所以把它们记录在这里)

Completely delete all copies of Xcode on your system. Restart your computer. Reinstall Xcode6-beta only. Verify that you still have the issue in playground and/or projects. Open iOS Simulator. Hardware -> Device -> Manage Devices Remove all devices. Recreate all devices you want. I appended the iOS version to the end of the name, just because. Restart Xcode and the simulator. Verify that at least playgrounds no longer throw issues when switched from OS X to iOS. Open your project and change the target's deployment target to something <= 7.1.

分析

看来问题是Xcode6不能正确地找到并连接到模拟器。我不知道为什么会出现这种情况，但这让我可以继续使用Swift进行开发。这可能与模拟器二进制文件似乎移动的事实有关。

当此错误开始弹出时，只需注释掉您编写的最后/最近的一段代码并等待一段时间。语法高亮显示应该会重新出现。这就是我解决这个问题的方法。

    func someFunc() -> (Int?, Int?, Int?) {
     var retVal1:Int? = nil
     var retVal2:Int? = nil
     var retVal3:Int? = nil

     //some other code

     //commenting out the line below helped me
     //(retVal1, retVal2, retVal3)
     return (retVal1, retVal2, retVal3)
    }

我的解决方案是更换模拟器。我使用的是iPhone 5S，当我切换到iPhone 5时，一切都很完美。希望未来的版本能完全修复它。