DEV Community

Cover image for ITMS-91053 Missing API Declaration: How to Add a Privacy Manifest to Your Expo App
Hugo Rus
Hugo Rus

Posted on

ITMS-91053 Missing API Declaration: How to Add a Privacy Manifest to Your Expo App

ITMS-91053 means your app uses iOS APIs that Apple calls "required reason APIs" (like UserDefaults or file timestamps) without declaring why in a privacy manifest (PrivacyInfo.xcprivacy). React Native apps almost always use some of them, through React Native itself or your dependencies. In Expo, you declare them under ios.privacyManifests in your app config, choose the reason code that matches your real use, update dependencies that ship their own manifests and rebuild.

You upload a build to App Store Connect, and an email arrives:

ITMS-91053: Missing API declaration - Your app's code in the "MyApp" file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDefaults. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app's privacy manifest...

Apple has been enforcing this since May 2024, so a missing declaration can now stop a submission. The fix is configuration, and it takes a few minutes once you know where it goes.

From LetsDeployIt, where we fix submission errors for AI-built and Expo apps.

What is a privacy manifest?

A privacy manifest is a file in your iOS app (PrivacyInfo.xcprivacy) that tells Apple:

  • Which "required reason" APIs your app uses, and why (NSPrivacyAccessedAPITypes)
  • What data the app collects (NSPrivacyCollectedDataTypes)
  • Whether the app tracks users and which domains are used for tracking (NSPrivacyTracking, NSPrivacyTrackingDomains)

ITMS-91053 is about the first part.

What are "required reason" APIs?

These are iOS APIs that could be misused to fingerprint devices, so Apple requires you to state an approved reason for using them. The four categories React Native apps hit most often:

API category Example use Common reason code
NSPrivacyAccessedAPICategoryUserDefaults Storing app settings (AsyncStorage on iOS, many SDKs) CA92.1
NSPrivacyAccessedAPICategoryFileTimestamp Reading file creation or modification dates C617.1
NSPrivacyAccessedAPICategorySystemBootTime Measuring elapsed time 35F9.1
NSPrivacyAccessedAPICategoryDiskSpace Checking free space before writing files E174.1

Each reason code has a specific meaning. CA92.1, for example, means "access user defaults to read and write information only accessible to the app itself". Pick the code that matches what your app actually does, using Apple's list of required reason APIs in its documentation. Don't copy codes blindly; the declaration is a statement about your app.

Why does my React Native app use these APIs?

You probably never called UserDefaults yourself. But:

  • React Native itself uses several of these APIs internally.
  • Popular libraries (storage, device info, analytics, crash reporting) use them too.
  • Apple scans the compiled app, so any code in the binary counts, whoever wrote it.

That's why almost every React Native app needs at least a few declarations.

How do I add a privacy manifest in Expo?

You don't create the .xcprivacy file by hand. Add an ios.privacyManifests section to app.json (or app.config), and Expo writes the manifest into the native project at build time:

{
  "expo": {
    "ios": {
      "privacyManifests": {
        "NSPrivacyAccessedAPITypes": [
          {
            "NSPrivacyAccessedAPIType": "NSPrivacyAccessedAPICategoryUserDefaults",
            "NSPrivacyAccessedAPITypeReasons": ["CA92.1"]
          },
          {
            "NSPrivacyAccessedAPIType": "NSPrivacyAccessedAPICategoryFileTimestamp",
            "NSPrivacyAccessedAPITypeReasons": ["C617.1"]
          },
          {
            "NSPrivacyAccessedAPIType": "NSPrivacyAccessedAPICategorySystemBootTime",
            "NSPrivacyAccessedAPITypeReasons": ["35F9.1"]
          },
          {
            "NSPrivacyAccessedAPIType": "NSPrivacyAccessedAPICategoryDiskSpace",
            "NSPrivacyAccessedAPITypeReasons": ["E174.1"]
          }
        ]
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Only include the categories listed in your ITMS-91053 email (or that you know your app uses), each with the reason that applies to you. Then rebuild:

eas build --platform ios --profile production
Enter fullscreen mode Exit fullscreen mode

A privacy manifest is native configuration, so it can't be delivered as an over-the-air update.

How do I check the generated manifest?

Generate the native project locally and look at the file:

npx expo prebuild --clean --platform ios
Enter fullscreen mode Exit fullscreen mode

Then open ios/<YourApp>/PrivacyInfo.xcprivacy. It should contain the entries from your config. (If your ios/ folder isn't committed, delete it again afterwards.)

What about third-party SDKs?

Apple maintains a list of commonly used third-party SDKs that must include their own privacy manifest (and, for some, a signature) inside the SDK. If an SDK on that list is outdated, your submission can be flagged even if your app's manifest is complete.

The fix:

  • Update your dependencies. Most maintained libraries added privacy manifests in 2024.
  • In Expo projects, use npx expo install --fix to move Expo-managed packages to versions that match your SDK.
  • For anything still flagged, check the library's issues and release notes for privacy manifest support, or replace it.

Is this the same as App Privacy labels?

No, and it's easy to mix them up:

  • The privacy manifest lives inside your app binary and declares API reasons, data collection and tracking at the code level.
  • App Privacy labels are the answers you fill in on App Store Connect, shown to users on your store page.

They should tell the same story. If your manifest says you collect crash data for app functionality, your App Privacy answers should say so too.

Troubleshooting

  • Still getting ITMS-91053 after adding the manifest: you're likely uploading an old build. Check the build number and that the build was made after the config change.
  • The email names a category you didn't declare: add that category with the matching reason and rebuild.
  • The email mentions a specific SDK: update or replace that dependency; your app-level manifest can't fix another SDK's missing one.
  • Not sure which reason fits: read the reason descriptions in Apple's documentation for that category and choose the one that matches your real use.

Checklist

  1. Read which API categories the ITMS-91053 email lists.
  2. Add each category to ios.privacyManifests with the correct reason code.
  3. Update dependencies (npx expo install --fix for Expo packages).
  4. Rebuild with EAS and upload the new build.
  5. Confirm the next processing email has no missing API declarations.
  6. Make sure your App Privacy answers in App Store Connect tell the same story.

Conclusion

ITMS-91053 looks alarming, but it's a declaration problem, not a code problem. React Native apps use a handful of "required reason" APIs, and Expo lets you declare them in a few lines of app config. Choose honest reasons, keep your dependencies current and rebuild.

If you'd rather hand submission issues off, LetsDeployIt takes Expo and AI-built apps through App Store and Google Play review until they're approved.

Which API category showed up in your ITMS-91053 email? Share it in the comments, along with the library that caused it if you found it.

Top comments (0)