yonaskolb / yonaskolb/XcodeGen

Multiple commands produce '/Users/kapil/Library/Developer/Xcode/DerivedData/Wellness360-eexhipqqmmpagyehznnbaveqdqrz/Build/Products/Debug-iphonesimulator/Wellness360.app/PrivacyInfo.xcprivacy'

Open
#1,533 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Swift
Stars
8.8k
Forks
908
Avg merge
17d 14h
Merged PRs (30d)
2

Description

Steps to Reproduce:

Add an external SDK (e.g., HealthFeedSDK) to the Podfile.
Run pod install.
Build the project in Xcode.
The build fails with the multiple commands producing PrivacyInfo.xcprivacy error.

What I Tried & Temporary Workaround:
Manually removing PrivacyInfo.xcprivacy from Copy Bundle Resources in Xcode allows the build to succeed.
However, this is not a permanent solution since it causes issues when building on TestFlight or CI/CD pipelines.
Expected Behavior:
pod install should not add duplicate PrivacyInfo.xcprivacy files in Copy Bundle Resources.
There should be a way to prevent these files from being added during Pod installation.

Environment:
Xcode Version: 16.0
macOS Version: Intel 14.6.1
React Native Version : 0.76.3
CocoaPods Version: 1.16.2
SDKs Used: pod 'HealthFeedSDK', :git => 'https://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@github.com/wellness360inc/hf-ios-sdk.git', :branch => 'auth-update'

Possible Fix:
Is there a way to automate removing PrivacyInfo.xcprivacy from Copy Bundle Resources after pod install?
Should this be handled via a post-install script in the Podfile?
Would appreciate any guidance on how to handle this properly without breaking the build on TestFlight! 🚀

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Podfile and the Xcode project's Copy Bundle Resources phase, then reproduce the failure by running pod install and building with HealthFeedSDK included. Compare the generated project state before and after installation; done means the duplicate PrivacyInfo.xcprivacy entries no longer produce a build failure, including in TestFlight or CI/CD builds.

Written by the indexing model from the issue text.

Assessment

Tech stack
react-native, swift
Domain
build-system, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.