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

我在苹果的开发者论坛上找到了一个解决方案(需要登录，所以我也会在这里解释)。

TLDR:不要在Objective-C中导入与@interface同名的@protocol到Swift桥接头。例如，Facebook SDK有一个名为“FBGraphObject”的协议和接口。

以下是论坛帖子:

Adding Facebook SDK causes SourceKitService to crash. If you want to use beta 3 and you need Facebook SDK, one work around that I found and is working for me is refactoring Facebook SDK's @protocol FBGraphObject and renaming it to something like @protocol FBGraphObjectProtocol as an @interface FBGraphObject also exists and apparently SourceKit doesn't like it. It sure is a temporary solution just to keep you functional and you'll have to use Cocoapods or otherwise build Facebook SDK yourself rather than using the framework library. For the time being, you'll need to make sure you don't have conflicting @protocol and @interface declarations and that includes 3rd party libraries you may be using. This cost me today, hope it helps! Posted by e.parto on July 10, 2014

对我来说(xcode 6.1)，原因是我忘记采用我的子类协议。

例如，这是错误的:

protocol SomeProtocol { ... }
class A :NSObject, SomeProtocol {
...
}
class B : A {
...
}

这是可以的:

protocol SomeProtocol { ... }
class A : NSObject, SomeProtocol {
...
}
class B : A, SomeProtocol {
...
}

将部署目标更改为iOS 8.0对我来说很有效。我知道有人说将它移动到<=7.1可以工作，但这个问题似乎来自多个来源，所以这个替代方案可能可以工作。

将扩展移动到主体类之前。

extension SomeType {
// new functionality to add 

}

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