Skip to content
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

PromiseKit-SwifterSwift_Privacy conflict with SwifterSwift-SwifterSwift_Privacy #1349

Closed
KavinKily opened this issue Sep 25, 2024 · 6 comments

Comments

@KavinKily
Copy link

xcode 15.4
when archive the project will show the error
Showing All Messages
Target 'PromiseKit-SwifterSwift_Privacy' (project 'Pods') has create directory command with output '/Users/xxx/Library/Developer/Xcode/DerivedData/xxx-bwmyfxhhjhmwbkbgrjpgazkmrkoo/Build/Intermediates.noindex/ArchiveIntermediates/xxx/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/SwifterSwift_Privacy.bundle'

Showing All Messages
Target 'SwifterSwift-SwifterSwift_Privacy' (project 'Pods') has create directory command with output '/Users/xxx/Library/Developer/Xcode/DerivedData/xxx-bwmyfxhhjhmwbkbgrjpgazkmrkoo/Build/Intermediates.noindex/ArchiveIntermediates/xxx/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/SwifterSwift_Privacy.bundle'

and when search the key workds SwifterSwift_Privacy.bundle in pods TARGETS PromiseKit-SwifterSwift_Privacy will show the result
image

@jiangyewen
Copy link
Contributor

fixed in this PR #1350

@akovalov
Copy link

Try to add dependency via SPM, not via CocoaPods. In our case, SwifterSwift and other SDK that used SwifterSwift were both via CocoaPods. Moving SwifterSwift to SPM resolved the issue.

@MJ-BEN
Copy link

MJ-BEN commented Nov 8, 2024

Version 8.1.2 still cannot solve this problem. In my project, both SwifterSwift and PromiseKit are used. When executing packaging, Xcode will still report the above error, and PromiseKit-SwifterSwift_Privacy still exists in the project.

@MJ-BEN
Copy link

MJ-BEN commented Nov 8, 2024

@akovalov Thank you very much, your method can effectively solve my problem.

@RomanPodymov
Copy link
Collaborator

Hello @MJ-BEN
The issue was already resolved, please try to use master instead of 8.1.2.

@MJ-BEN
Copy link

MJ-BEN commented Nov 8, 2024

@RomanPodymov Thanks for your reply, unfortunately I can't use the master branch. According to our library management rules, I need to specify the version of each library, so I solve this problem by specifying commit now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants