Rejection guides / ITMS-91053: Missing API declaration (privacy manifest)
ITMS-91053: Missing API declaration, and how to fix your privacy manifest
This isn't an App Review rejection. It comes from App Store Connect when you upload, because your app or an SDK uses an API that needs a declared reason in a privacy manifest.
"Starting May 1, 2024, apps that don't describe their use of required reason API in their privacy manifest file aren't accepted by App Store Connect."Describing use of required reason API (Apple developer documentation), Apple
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
What it means
Apple lists some APIs as "required reason" APIs, because they could be used to fingerprint a device. If your app or anything bundled in it calls one, the app needs a privacy manifest file, PrivacyInfo.xcprivacy, that names the API category and an approved reason code.
The email from App Store Connect names the API category, such as NSPrivacyAccessedAPICategoryUserDefaults, and often the file or framework that references it.
The categories and common reason codes
- UserDefaults (NSPrivacyAccessedAPICategoryUserDefaults): CA92.1 for reading and writing data only your app can access.
- File timestamps (NSPrivacyAccessedAPICategoryFileTimestamp): C617.1 for files inside your app or app group container, DDA9.1 to display timestamps to the person.
- System boot time (NSPrivacyAccessedAPICategorySystemBootTime): 35F9.1 to measure time elapsed between events in the app.
- Disk space (NSPrivacyAccessedAPICategoryDiskSpace): E174.1 to check there's enough space to write files, 85F4.1 to display disk space to the person.
- Active keyboards (NSPrivacyAccessedAPICategoryActiveKeyboards): 54BD.1 to adjust your UI to the active keyboard.
Pick the code that truthfully describes your use. Each reason has conditions, such as not sending the data off the device. Apple's documentation lists every code and its rules.
How to fix it
- In Xcode, add a new App Privacy file (PrivacyInfo.xcprivacy) to your app target if you don't have one.
- Under Privacy Accessed API Types, add one entry per category named in the email, each with its reason code.
- Update third-party SDKs. Many popular SDKs, including Firebase, Alamofire, Flutter and OneSignal, are on Apple's list of SDKs that must ship their own privacy manifest and signature.
- For Flutter, React Native and Capacitor apps, the reference can come from a plugin. Update plugins, and add the declaration to the app's manifest if a plugin still lacks one.
- Archive and upload again. In Xcode's Organizer you can generate a privacy report to check what the combined manifests declare.
Common questions
- Is ITMS-91053 a rejection?
- It's an upload issue from App Store Connect, not a decision by an App Review reviewer. Fix the privacy manifest and upload a new build.
- I don't call UserDefaults directly. Why am I getting this?
- Almost every SDK uses UserDefaults. The reference may come from a framework you include. Updating the SDK, or declaring the category in your app's manifest, resolves it.
- What about ITMS-91061?
- ITMS-91061 is about a listed third-party SDK missing its own privacy manifest. Updating that SDK to a version that includes one is the usual fix.
Get your own rejection explained
Paste the message from App Store Connect or Play Console. Free, no account, about ten seconds.
Related guides
- Guideline 5.1.1(i): Privacy policy and permission strings
- Guideline 5.1.2(i): Data Use and Sharing (tracking, ATT, third-party AI)
- Guideline 2.5.1: Software Requirements (public APIs and frameworks)
Apple decides every review. These guides explain what the guidelines say and what usually helps. They can't promise an approval.
Sources: Describing use of required reason API (Apple) · Third-party SDK requirements (Apple)