ITMS-91061

ITMS-91061: Missing Privacy Manifest

ITMS-91061 is the painful version of privacy manifest work: you learn during upload that a framework or SDK needs a PrivacyInfo.xcprivacy file. StoreShield surfaces those gaps from the archive first.

Try Pro free Mac App Store

7-day trial applies to the Direct DMG only. Mac App Store subscriptions are managed by Apple.

Why the error happens

Since Apple's privacy manifest enforcement, apps and listed third-party SDKs need manifest coverage that matches the binary being submitted.

✓ The main app bundle can be missing PrivacyInfo.xcprivacy.
✓ An embedded SDK can be on Apple's manifest-required SDK list.
✓ A framework can expose privacy or Required Reason API signals without matching manifest evidence.

What StoreShield inventories

The SDK and Privacy gates show which bundle path created the risk so the owner can fix the right target.

✓ Embedded frameworks, bundles, and SDK identifiers.
✓ PrivacyInfo.xcprivacy presence by app and SDK path.
✓ Apple-listed SDK manifest checks with release-ready evidence.

How to resubmit with confidence

The export is designed for release handoff, not just debugging.

✓ ITMS_ERRORS_MAPPED.md when you import the Apple diagnostic.
✓ Reviewer notes draft and fix plan for the release owner.
✓ Machine summary and SARIF for teams that want CI visibility.

FAQ

Can StoreShield fix a vendor SDK manifest automatically?

No. StoreShield identifies the missing manifest risk and exportable evidence. Vendor SDK updates or manual manifest work still need to happen in the app project.

FAQ

Does StoreShield need App Store Connect access?

No. The scan is local. You can optionally paste the ITMS email or Transporter log to map the exact Apple diagnostic.