[pod_target_dependency_installer] Allows generation of static framework with resource files #12357
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.
馃寛 Hi, committers,
As mentioned in this issue, it is no longer possible to generate static framework targets that contain resource files in CocoaPods 1.7 and above.
This change might not cause a problem, because static frameworks did not need to be embedded in the application normally. However, the situation changed when Apple required support for privacy manifests.
According to Apple, if you want to distribute an application using a third-party SDK that supports privacy manifest as a static library, you need to create a static framework that includes the privacy manifest file. However, the current CocoaPods cannot generate such a static framework target. Even if you write the
resource_bundle
specification in the podspec, the "Copy Bundle Resources" field in the build phases of the generated static framework target will be empty.To solve this problem, I have created this pull request that make possible to include resource files in static framework targets.
I hope you will approve this change.