This is not working as described, then. I received a warning email about a missing API declaration for a widget extension that was already declared in the host app, so I added a separate privacy info file for the extension, and that fixed it. We also have one that is being triggered by a third-party SDK, and I have no idea how to go about fixing that one besides just hard-coding it into the widget's manifest file.
rsippert
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
Last seen
User for
Post
Replies
Boosts
Views
Activity
Do we need to resort to adding those reasons to our app's manifest? Which seems hacking since we probably don't know when of the allowed reasons are accurate.
This may not be possible for some of these. For example, our app has two missing API declarations flagged in our widgets extension, which must be coming from third-party code because one of them is for UserDefaults which we are already declaring in our app. According to Apple's documentation, we should not need a separate privacy manifest for widgets, so adding one to address this seems like it would not work.