Use separate privacy bundle name to avoid conflicts with standalone ZIPFoundation#14
Merged
Merged
Conversation
mickael-menu
approved these changes
Nov 6, 2025
mickael-menu
left a comment
mickael-menu
left a comment
Member
There was a problem hiding this comment.
Looking good, thank you for this fix.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using both ReadiumZIPFoundation (this fork) and the standalone ZIPFoundation pod in the same project, Xcode fails to build with the following error:
Multiple commands produce '/path/to/DerivedData/.../ZIPFoundation_Privacy.bundle'Changes proposed in this PR
ReadiumZIPFoundation_PrivacyFurther info for the reviewer
A workaround I had to implement was to manually delete the
ZIPFoundation-ZIPFoundation_Privacytarget in a CocoaPods post_install hook and patch the generated copy scripts to remove references to the deleted bundle.If the privacy bundle was just renamed to align with the fork's name, this is not needed