@kimjitae I believe it should work as far as Apple does not know you did that, because when I had a discussion with the Code Level Support team they said this is not acceptable and will be rejected, but I asked them so how could you know if i did that? they didn't answer. I believe they even don't know that this is the only way we can do it, or Apple must deprecate the Static-Library targets.

@kimjitae That is what I've told Apple Code Level Support Team, I told them since you still support StaticLibraries in Xcode I don't see a reason why I should not use them. especially they are quite practical and easy to build and use/debug. Hope I was able to provide you with all what you need to unblock your project. If I have new information I will try to post it here, but so far they stopped responding and last answer was to insist on using XC Static Framework for adding Privacy Manifest!!!

They said there is no way to add a privacy manifest file to a static library. if you have to do that you must move to use XC Static Framework (wrap your static library with an XC Static Framework) and then you can add a privacy manifest file.

Looks like you are using XC Static Framework and not a Static Library. if this is the case that is completely different and you will have no problems if you add your privacy manifest correctly to your XC Static Framework. I believe that there are some guides to show how to add XCPrivacy file to an XC Static Framework but I am not there yet to be honest and I can't recommend one since I am not using Static Framework.

Did your team add 'Privacy Manifest' to the app level? ==> yes I mean we tried adding it to the App Level Privacy Manifest file and it worked for now, but we all know that this may not be guaranteed forever especially it is still now not applied completely and that is just a warning. soon we will know what Apple will say about it in reality. There's still a lot I don't know. What does the above mentioned "linker" mean? ==> I mean for the Linker used in Xcode to link static-lib with the app

and based on my experience adding it to the AppLevel privacy manifest worked for us for the current time but who knows what change could come from Apple AppStore Connect side to reject that!

After discussion with Apple Code Level Support Team, they said this is not following Apple requirements. the manifest file is to represent what we use in the SDK itself (static-lib) and not in the app. so that may not pass if they know about it, however I believe it is hard they know without changing the linker :)

No one has answered yet, and I am trying to communicate with Apple, they told me to communicate with the Code-level support team to get an answer and that is really not very easy, they are asking about many details to submit a request where I really don't need them like logs and sample code the question is quite clear and easy, and they are not answering I submitted the app to AppStore with the StaticLibrary, but I got no warnings even while I expected the app to be accepted with some Warnings