I'm looking into Privacy Manifest as an Apple policy change.
I have a problem here.. some of the libraries I use are no longer updating. (e.g. GCDWebServer)
I can't find a library to replace it, so I'm going to fork the library, and I'm going to add Privacy Manifest.
I will download the fork library into my Mac and search the entire API list announced by Apple above through Xcode one by one.
If I find a problem API, I will add it to Privacy Manifest. Is this a good way to do it???
Is there any better way??
Now many people know how to do it, but I'll answer it myself to close the question.
If App have a problem with Privacy Manifest, we will receive an email from Apple. And we can supplement that and resubmit it.
It's simple to make sure that Apple's Privacy Manifest policy is properly applied. We can get emails from TestFlight external deployments or App Store deployments. We get emails every time we deploy a new build version. (If you haven't received the mail, you don't have to worry.)
To solve PrivacyManifest, add PrivacyInfo to your problematic project or library.
If it's an open source library, you can ask the developer or add it through Fork. If we're project owners, we can add it ourselves.
We can find out what we want to add to Privacy Manifest either directly through the project code or through Apple mail.