Although, the app may still be launched in the background. So, the first thing to do is to fix the bugs in your app. What if the bugs only occur when the app is launched in the background state? Is there a way to test this deterministically?

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.

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.