What the error means
Start with the exact path in Apple’s email. An app can contain multiple manifests, and a valid main-app file does not repair an invalid manifest inside a framework.
Common causes
How to fix it
- 1Locate the manifest path Apple named, including manifests nested inside frameworks.
- 2Paste or upload that XML file into the local validator.
- 3Correct structural errors first, then review every item marked Developer confirmation.
- 4Run plutil -lint locally and validate the archived product before the next upload.
Apple documentation
FAQ
Frequently asked questions
What causes ITMS-91056?
Common causes include malformed XML, unknown keys, incorrect plist types, invalid tracking-domain strings, empty arrays, and category/reason mismatches.
Why does plutil pass when App Store Connect rejects the file?
plutil checks property-list syntax. App Store Connect also validates Apple-specific keys and allowed values.
Can tracking domains contain https://?
No. Apple expects a domain or subdomain only, with no protocol, path, query, fragment, port, or trailing slash.
Which manifest should I fix?
Fix the exact file path in Apple’s email. It may belong to the app or to a bundled third-party framework.
Check the actual email and manifest
Get evidence, source classification, fix steps, and a locally generated correction draft. No login and no file upload.
Open the free checker