I have a project that generates a fat Static Library (NOT a Static XC Framework), and the output of that project would be a single static library file let us say: "libProject.a" We are distributing this "libProject.a" to our clients and we are not using XC Frameworks yet.
For this specific case of having Static Library, do we need PrivacyInfo.xcprivacy file to be distributed with it? and in case it is required, how is it supposed to be distributed with the Static Library? is it enough for the ones who are using this library in their projects to add the missing XCPrivacy entries to their app "PrivacyInfo.xcprivacy" file ?
PS: I know ideally it would be better to use Static Framework instead of Static Library but that is still planned in our schedule for a future release, Since "Static Library" target type is still supported by Xcode 15.2 that means there must be a solution.
If i submit an app without adding anything to 'PrivacyInfo'
I get an email saying that the APIs used by the static library (.a) are problematic.
And through this email, I added the contents to the app's 'PrivacyInfo'.
When I resubmitted it, I didn't get an e-mail.
For this policy to be meaningful
When creating and distributing static libraries, it seems good to distribute 'PrivacyInfo' content clearly to users.
If the API you use is a static library and an app at the same time, the contents of the library will be resolved automatically as the app developer adds the contents of the app.