What is "ITMS-91053: Missing API declaration" Error and How to Resolve It?

The ITMS-91053 error is a notification from Apple indicating that your app’s code references APIs that require a declaration in the app’s privacy manifest.

To resolve this, you must include an NSPrivacyAccessedAPITypes array in your app’s privacy manifest file named "PrivacyInfo.xcprivacy," located at the package root. This file should clearly declare the APIs your app uses and provide approved reasons for their use.

For detailed guidelines, refer to Apple’s documentation on Describing the Use of Required Reason API.

For example, if your app uses the NSUserDefault API, your privacy manifest file could be structured as follows:

sample of PrivacyInfo.xcprivacy file located at your Xcode project root location

In this example, the reason CA92.1 is declared for accessing user defaults to read and write app-specific information. Other possible reasons include 1C8F.1 for App Group specific data, C56D.1 for third-party SDKs wrapping user defaults API(s), and AC6B.1 for reading or setting keys for managed app configurations.

The current list of API categories that might require declaration includes:

• NSPrivacyAccessedAPICategoryFileTimestamp
• NSPrivacyAccessedAPICategorySystemBootTime
• NSPrivacyAccessedAPICategoryDiskSpace
• NSPrivacyAccessedAPICategoryActiveKeyboards
• NSPrivacyAccessedAPICategoryUserDefaults

Note that this list could evolve over time, so it's important to stay updated with Apple's documentation for any changes.

Additionally, developers providing SDKs or libraries must ensure that their packages also declare API usages in compliance with this policy. This is crucial to avoid compliance issues for apps incorporating these SDKs or libraries, ensuring that the privacy manifest accurately reflects the usage of APIs as per Apple's guidelines.

If you encounter the ITMS-91053 error due to SDKs or packages used in your app, it is advisable to update these components, as many library developers have already included the necessary privacy manifest files in their packages. If the error persists after updating, check the SDK's or package's repository for open issues related to this error. In case there are no existing issues, consider opening a new issue to bring this to the attention of the maintainers. Prompt action by library developers in addressing these privacy manifest requirements is crucial for ensuring that all apps using their libraries are compliant with Apple's guidelines.

By adhering to this protocol from May 1, 2024, developers can ensure their apps meet Apple's privacy requirements, enhancing user trust and app integrity on the App Store.