CODEWITHSUNDEEP
iosswiftxcodexcode7xctest
fancy
fancy

Reputation: 2149

iOS Unit Testing: Class is implemented in both

I'm building an iOS 9 App with Swift 2 and Xcode 7.

My app runs fine when deploying it to my phone but when I run any unit test, I get the following error message for a lot of classes:

Class _TtC5<AppName>19<ClassName> is implemented in both /Users/<Username>/Library/Developer/CoreSimulator/Devices/<UUID>/data/Containers/Bundle/Application/<UUID</<AppName>.app/<AppName> and /Users/<Username>/<Path/To/Workspace>/DerivedData/<AppName>/Build/Products/Debug-iphonesimulator/<AppName>.xctest/<AppName>. One of the two will be used. Which one is undefined.

Any ideas?

Upvotes: 7

Views: 6118

Answers (4)

Mundi
Mundi

Reputation: 80265

Only add the test class to your test target and none of the iPhone app classes. Then simply import your app name as a module on top of your test class to get access to all app classes.

@testable import MyAppName

Upvotes: 7

rustyMagnet
rustyMagnet

Reputation: 4085

I had the same error with an XCTest. Remember to select Allow testing Host Application APIs.

enter image description here

Then inside of Build Phases for your XCTest Target - like others have said - make sure you have zero files in Compile Sources that are already compiled in the Host Application.

Upvotes: 3

ricardopereira
ricardopereira

Reputation: 11683

Duplicated class implementations while running the test suite: in my case, since the test target has a host app, you don’t need to link the third-party frameworks. I had to clean the "Other Linker Flags" (OTHER_LDFLAGS) from Build Settings because it was linking to all CocoaPods of the workspace.

Upvotes: 4

Roberto
Roberto

Reputation: 3839

The answer by @Mundi is correct for some cases.

However, I experienced the same error and what was causing it is that the libPods.a file for Cocoa Pods was being linked in the app target and the test target.

Upvotes: 2

Related Questions