Starting March 13: If you upload a new or updated app to App Store Connect that uses an API requiring approved reasons, we’ll send you an email letting you know if you’re missing reasons in your app’s privacy manifest. This is in addition to the existing notification in App Store Connect.
Does this mean that if you do not receive a warning email when an app is uploaded to Testflight, it means that the app has completed the necessary privacy list settings. Can pass the review normally. At present, our app has updated SDKs such as Firebase in the blacklist SDK. After uploading once, no warning email was received.
zhaojb
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
@DTS Engineer
Sorry, my description is wrong. Since the SDK for secondary packaging uses pod to reference Firebase in the form of source code, what ultimately needs to be signed is actually our own SDK.
The final summary is as follows:
The SDK developer of the binary distribution cannot confirm the source code, so the packager needs to sign it to confirm whether the SDK has been tampered with.
Since Firebase pod is a source code reference, when performing secondary distribution of the SDK, the person who ultimately distributes the SDK needs to sign his or her own SDK.
Hope it helps anyone who encounters the same problem.