Class X is implemented in both <framework> and <application> one of the two will be used, which one is undefined

class pflogger is implemented in both
class sdltranslatorresponder is implemented in both
class rxobjcruntime is implemented in both
class qnsstatusitem is implemented in both
class supowerassertionmanager is implemented in both
class deallochook is implemented in both
class itnsimage is implemented in both
class adobesimpleurlsession is implemented in both

I'm getting this warning:

Class X is implemented in both <framework> and <application> one of the two will be used, which one is undefined

This warning is covered quite a bit across the web but i haven't found anything that answers the specific problem I'm having.


I've built MyFramework and MyApplication (as a test/demo application for MyFramework).

MyFramework uses a CocoaPod (which I'll refer to as CoolPod), which I also want to use in MyApplication (and it is reasonable to assume a consumer of MyFramework would also).

I need to be able to distribute MyFramework as a .framework (for closed source). However, this means that MyFramework embeds CoolPod in its compiled library.

Now when I import MyFramework and CoolPod into MyApplication I get this conflict (outputting the warning shown above) as CoolPod's classes are already included in MyFramework's library (as CoolPod is embedded).

So we have this structure:

CoolPod -> MyFramework \
               CoolPod /


How do I avoid this conflict?

  • Is there a way to my MyApplication provide CoolPod to MyFramework?
  • Do I have to pipe CoolPod's headers through MyFramework?

I've thought about including CoolPod's headers (but not its lib) in MyApplication, however this seems overly complex for what should be a simple case.

Any help is greatly appreciated, this is really blocking me right now.



For closed-source static libraries we recommend cocoapods-packager. I'm not sure it's support for frameworks though.

ios, For closed-source static libraries we recommend cocoapods-packager. I'm not sure it's support for frameworks though. In either case, and in both classes and structs, your implementation should follow the five guarantees of equivalence (For the following rules, assume that x, y and z are not null): x.Equals (x) returns true. This is called the reflexive property. x.Equals (y) returns the same value as y.Equals (x).

My solution was to take the source code from the cocoa pod and create a Cocoa Touch Framework for it. Then I linked the framework to my api and to my test app. This isn't great but it is all I could do quickly. I believe Cocoapods is working on supporting frameworks so this solution may get outdated soon enough.

My company also uses gradle for dependencies (java) and build scripting. So I created a groovy/gradle build task that builds my framework and my supporting frameworks (cocoapod frameworks) and creates a universal framework from them. Then it zips all of the frameworks. This means I can distribute one zip with all of the requirements. This obviously isn't the nicest way to distribute (we'll be moving to distributing through Cocoapods with dependencies on our closed source frameworks), but it is fast to setup.

Class is implemented in both (), Class is implemented in both () I have seen that in the past, but in my situation I don't get why.. - I have a static OS X framework, let's call it  To declare a class that implements an interface, you include an implements clause in the class declaration. Your class can implement more than one interface, so the implements keyword is followed by a comma-separated list of the interfaces implemented by the class. By convention, the implements clause follows the extends clause, if there is one

One solution is to turn on use_frameworks! in the framework's Podfile. Then you still could make your framework compiled, and embed your framework in the target app. The warning messages will disappear (It is simply because framework's pods are complied to another framework, but you don't embed this one in your target app. Then your app will refer to the binary of its own.)

But this is not a good solution for two reasons: 1. You need to make sure the target app include the necessary pods that the framework needs. 2. The app might use different pod version to the framework. If both framework and app refer to the same pod binary, it could lead to crash.

I doubt there is a good solution for this issue.

Class is implemented in both /Syst…, I have tried my app on severals devices but some of theme show this error in Xcode console: objc[8430]: Class DeviceType is implemented in both  Explicit interface implementation also allows the programmer to implement two interfaces that have the same member names and give each interface member a separate implementation. This example displays the dimensions of a box in both metric and English units.

If you want a quick solution - just add your MyFramework project as a subproject to MyApplication project. You can still use cocoa pods both for your framework and test application (but include your "common" lib with pods only to framework project)

Without use_frameworks!, "implemented in both" loader errors , [X ] I've read and understood the *CONTRIBUTING guidelines and have Class PodsDummy_GoogleToolboxForMac is implemented in both  Similarly an Animal class doesn’t have implementation of move() (assuming that all animals move), but all animals must know how to move. We cannot create objects of abstract classes. A pure virtual function (or abstract function) in C++ is a virtual function for which we don’t have implementation, we only declare it.

You can create a Podspec for your MyFramework with CoolPod as a dependency.

Your MyFramework.podspec will look something like: do |spec|          = 'TestFW'
  spec.version       = '1.0.0'
  spec.license       = { :type => 'BSD' }
  spec.homepage      = ''
  spec.authors       = { 'Auther Name' => '' }
  spec.summary       = 'Testing FW Pod with Test App'
  spec.source        = { :git => '' }
  spec.module_name   = 'TestFW'
  spec.ios.source_files   = 'TestFW/*.swift'

  spec.dependency 'CoolPod'

And your MyApplication's podfile will look something like this:

target 'TestApp' do

  pod 'CoolPod'
  pod 'TestFW'

class x is implemented in both /usr/local/Cellar/ and /Applications , xcodebuild -version Xcode 8.3.2 Build version 8E2002 » fbsimctl list Class _TtCs18_EmptyArrayStorage is implemented in both  Process for NAND Implementation 1. If starting from a logic expression, implement the design with AOI logic. 2. In the AOI implementation, identify and replace every AND,OR, and INVERTER gate with its NAND equivalent. 3. Redraw the circuit. 4. Identify and eliminate any double inversions (i.e., back-to-back inverters). 5. Redraw the final

The Semantic Web: Research and Applications: Second European , results when executed against the model in the example: the first result is the mapping ?a → : X and The second step, i.e. the implementation of both single nodes and chains detection, has been completed as a Java class (again using the  An interface should be implemented by both the real class and the mock class to guarantee that the mock class accurately simulates the real class when used in a program. Which of the following statements about a mock class is true?

TinySolution: Fix CocoaPods duplicate implement warning, Some Classes are implemented repeatedly, so although there is no problem with the operation for Class AFXXX is implemented in both . Generic Interfaces (C# Programming Guide) 07/20/2015; 4 minutes to read +4; In this article. It is often useful to define interfaces either for generic collection classes, or for the generic classes that represent items in the collection.

Algorithms, 10th Annual European Symposium, Rome, Italy, September 17-21, 2002, Proceedings Esa Algebraic Numbers and Conics: We have implemented four classes: We checked the correctness of the implementation both manually (for small  abstract class X implements Y { // implements all but one method of Y } class XX extends X { // implements the remaining method in Y } In this case, class X must be abstract because it does not fully implement Y, but class XX does, in fact, implement Y.

  • I have a similar issue, did you find a solution?
  • Similar issue, but with unit tests, is discussed here:…
  • Surprising — isn't this a really common pattern? Don't developers want to be able to create DAGs of compilation units without worrying that there are gonna be collisions?!
  • Hi @Zenton. Besides the accepted answer, did you manage to solve this issue with a different solution? I'm facing the same issue, I would appreciate your advice.
  • I wasn't able to make this approach work - the app target won't link, with "Symbol(s) not found for architecture arm64" for any classes defined in the pods included only in the framework. Any ideas?
  • This worked for me. I just had to delete my derived data to get it to work