How to Support for Static Library(.a) Privacy Manifest

Our team uses a static library (.a) consisting of C and C++.

  1. Our team is developing static libraries internally and not sharing them to the outside. Should we still provide 'Privacy Manifest' in this case??

  2. I added the contents of our team's static library (.a) to the app's 'Privacy Manifest' and there was no problem.

  3. Nevertheless, if I have to add it separately to the static library (.a), should I create a new framework project itself and not use the .a? Or can I just create a new framework and wrap the .a file??

Apple has updated the documentation some time in the last week. Your question may be answered in the new page:

How to Support for Static Library(.a) Privacy Manifest
 
 
Q