APP STORE ERROR
ITMS-91056: inspect the privacy manifest before resubmission.
When App Store Connect reports an invalid privacy manifest, start with the PrivacyInfo.xcprivacy structure and the exact bundle or SDK that contains it rather than guessing from a generic fix.
STRUCTURE
Check each accessed API dictionary
A privacy manifest can be present and still be invalid. Review the NSPrivacyAccessedAPITypes structure and make sure each accessed API type has the expected reasons array and valid values.
LOCATION
Confirm which bundle owns the manifest
Apps and third-party SDKs can each ship privacy manifests. Identify the bundle or dependency that App Store Connect is evaluating before changing the app-level file.
PREFLIGHT
Catch obvious repository gaps before another upload
AccessVerdict can flag obvious structure gaps and relevant SDK inventory from repository text, then rerun the same check after you change the manifest.
FINAL
Use Apple's TN3181 for the final diagnosis
Apple Technical Note TN3181 documents debugging invalid privacy manifests. Static repository analysis is advisory; the submitted build remains authoritative.