Our team uses a static library (.a) consisting of C and C++.
Our team is developing static libraries internally and not sharing them to the outside. Should we still provide 'Privacy Manifest' in this case??
I added the contents of our team's static library (.a) to the app's 'Privacy Manifest' and there was no problem.
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??
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
Privacy
Frameworks