What the error means
Do not copy the SDK’s declarations into the main app manifest as a workaround. Apple requires the SDK bundle that contains the code to provide its own manifest.
Common causes
How to fix it
- 1Extract the exact SDK name from the rejection email and confirm the version in the archived app.
- 2Upgrade to the vendor’s latest compatible release and confirm the SDK bundle contains PrivacyInfo.xcprivacy.
- 3If no compliant release exists, contact the vendor or replace the dependency.
- 4Rebuild from a clean dependency resolution and inspect the final archive before upload.
Apple documentation
FAQ
Frequently asked questions
What does ITMS-91061 mean?
App Store Connect found a third-party SDK that requires a privacy manifest, but the expected manifest was missing from the SDK bundle.
Can I add the SDK declaration to my main app manifest?
No. Apple says a third-party SDK cannot rely on the app’s manifest to report the SDK’s Required Reason API use.
What if the latest SDK still has no manifest?
Contact the vendor for a compliant release or replace the dependency. Hand-editing a binary dependency is fragile and can invalidate SDK integrity expectations.
Does deleting the SDK from package configuration fix the archive?
Only if the SDK binary is actually absent from the final archive. Inspect the built product rather than relying only on dependency declarations.
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