-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Multiple commands produce xxxx ] happened while archiving app(target >= iOS11) , with Clips or Widgets in iOS14 #1522
Comments
Kingfisher's SwiftUI support is a part of (or say an additional slice) the core framework. So if you are using |
But the |
I got your idea. I pushed some changes to the
|
No, still not work
Also you can find these two frameworks are all added into Pod target with the same name: Kingfisher. |
Here is the Podfile I am trying and it works fine. CocoaPods recognized both as a single target in the pod framework. Maybe check your project setting or Podfile to see if there is another setting causes this issue. |
And the target name in your log is suspicious, if you are not pasting it wrongly. |
yep, and I fixed the dependency in my private pods and it works. |
For those who are struggling with this error after upgrading to 5.15.7: Remember to install only
it'll produce the same error, just use
|
Just tried it got: [!] Unable to find a specification for You have either:
here's my pod file:
|
I'm working with the project:
Main project working with the latest Kingfisher and development target = iOS 11.
Clip / Widget extension working with the latest Kingfisher/SwiftUI and development target = iOS 14.
After pod installing, the Kingfisher and Kingfisher-Core-SwiftUI target is added into the Pods project, and their Product Name are both Kingfisher.
So when I archive the app , the error occurs due to the same Product Name of them:
I know that it's not the issue or bug with Kingfisher, but can u provide me some solution in this situation?
Thx
The text was updated successfully, but these errors were encountered: