Open szotp opened 3 years ago
I have the same problem, but I'm using a private developer pod (which is my app's SDK) that includes xcframework libraries like Alamofire, AWS, RxSwift, Realm, etc.
I was able to repro the initial report. Yes this is a bug with subspecs because they are de-duped between different targets that use them however they produce the same framework name always.
Actually @szotp this seems to be building for me on 1.11.0 (master branch). 1.11.0 has not shipped yet but it will soon.
Going to try 1.10.2 now.
I think @marciogranzotto post is a different issue fixed in 1.11.x.
oh I see this is just a warning not a build failure, nevermind.
we can possibly solve this via https://github.com/CocoaPods/CocoaPods/issues/8206#issuecomment-907492786
Report
What did you do?
In the example I have used 3 different projects (to ensure it's not related to specific libary): MaterialComponents, AFNetworking, PromiseKit.
MaterialComponents: target names have this weird suffix
AFNetworking: target names are different, but framework names are the same
PromiseKit subspecs are exactly the same on both targets, and problem does not occur.
What did you expect to happen?
Valid Pods project is generated.
What happened instead?
Targets & frameworks are duplicated:
And during build, I'm getting these warnings:
A workaround is to use the same subspecs on both targets, even if I don't need them (as shown with PromiseKit).
CocoaPods Environment
Stack
Installation Source
Plugins
Podfile
Project that demonstrates the issue
MinimalExample.zip