All posts

iOS privacy manifest: fix 'missing API declaration'

· 7 min read

You upload an iOS build to App Store Connect, and an email from Apple follows. It says your app uses an API that needs a declared reason, and your privacy manifest does not list one. You may never have heard of a privacy manifest. This post explains what it is in plain words, what the "required reason" part means, and how to check before you upload. I checked Apple's and Expo's pages in November 2026. They change, so look again before you rely on them.

Short answer: add a file named PrivacyInfo.xcprivacy to your app. In it, list each category of required reason API your code uses, with an approved reason code for each. Update your third-party SDKs, because they may need their own manifests. Then run Xcode's privacy report before you upload.

Why Apple sends this email

Apple's news post from February 29, 2024 set the dates. From March 13, an upload that uses an API needing approved reasons gets an email if reasons are missing. From May 1, you need "approved reasons for the listed APIs used by your app’s code" to upload a new or updated app. Apple's Describing use of required reason API page says the same: "Apple sends you an email reminding you to add the reason".

I won't quote the email's error code or wording, because the pages I checked do not publish it. If your email names an API, that API is the one to declare.

What a privacy manifest is

Apple's Privacy manifest files page says apps and SDKs can contain "a privacy manifest file, named PrivacyInfo.xcprivacy". It is a property list, which is an XML file. It records two things: the types of data your app collects, and the required reason APIs it uses. In Xcode you add it with File > New File, then the App Privacy File type in the Resource section. The page calls the default name "the required file name for bundled privacy manifests". Add the file to your target, so Xcode uses it.

These are the top-level keys the page lists:

  • NSPrivacyTracking: a Boolean for whether you use data for tracking under App Tracking Transparency.
  • NSPrivacyTrackingDomains: the internet domains you connect to that engage in tracking.
  • NSPrivacyCollectedDataTypes: the data types you collect.
  • NSPrivacyAccessedAPITypes: the required reason API categories you use, with reasons.
<key>NSPrivacyTracking</key>
<false/>
<key>NSPrivacyTrackingDomains</key>
<array/>
<key>NSPrivacyCollectedDataTypes</key>
<array/>
<key>NSPrivacyAccessedAPITypes</key>
<array>
  <dict>
    <key>NSPrivacyAccessedAPIType</key>
    <string>NSPrivacyAccessedAPICategoryUserDefaults</string>
    <key>NSPrivacyAccessedAPITypeReasons</key>
    <array>
      <string>CA92.1</string>
    </array>
  </dict>
</array>

That is the inside of the top-level dictionary, for an app that only uses UserDefaults for its own settings. Your real file needs your real answers.

Required reason APIs

Apple's page explains why these exist: some APIs "have the potential of being misused" to identify a device, which is fingerprinting, and "fingerprinting is not allowed". So for each category you use, you must "declare one or more approved reasons that accurately reflect your use". Apple's NSPrivacyAccessedAPIType page lists the categories today:

  • File timestamp: NSPrivacyAccessedAPICategoryFileTimestamp
  • System boot time: NSPrivacyAccessedAPICategorySystemBootTime
  • Disk space: NSPrivacyAccessedAPICategoryDiskSpace
  • Active keyboards: NSPrivacyAccessedAPICategoryActiveKeyboards
  • User defaults: NSPrivacyAccessedAPICategoryUserDefaults

Each category has its own reason codes. For user defaults, code CA92.1 covers reading and writing information that only your app can reach: Apple describes it as information "only accessible to the apps, app extensions, and App Clips that are members of the same App Group as the app itself". Plenty of apps use that one without knowing, because saving a setting or a seen-onboarding flag goes through UserDefaults. Apple's page says it continually reviews the list and will update it, and that the reason must match what your app really does. If none of the listed reasons fit, the same page has a link to ask Apple for a new one. Do not pick a code that is just close enough.

Third-party SDKs

Your app includes other people's code, and your upload checks it too. Apple's Third-party SDK requirements page says you are "responsible for all the code the SDK includes in your app". It has a list called "SDKs that require a privacy manifest and signature". A few names from it: Alamofire, FirebaseCore, FirebaseAuth, GoogleSignIn, FBSDKCoreKit, Lottie, SDWebImage, OneSignal, Capacitor, Cordova, hermes, Flutter, and plugins such as shared_preferences_ios, path_provider_ios and url_launcher_ios. The page says "Any version of a listed SDK, as well as any SDKs that repackage those on the list, are included in the requirement." Signatures matter when the SDK is a binary dependency.

The February news post adds: "Make sure to use a version of the SDK that includes its privacy manifest". So update your SDKs first, then check what is left. To see what your app includes, open your Podfile.lock or Package.resolved, or your package.json and pubspec.lock, and compare the names against Apple's list.

Apple says Xcode will "combine the privacy manifests across all the third-party SDKs used by your app into a single, easy-to-use report". That is the report in the next section.

Expo, React Native and Flutter

Expo's privacy manifests guide says you can add one with "the privacyManifests field under expo.ios in your app config". Its own example is the same UserDefaults entry as above:

"ios": {
  "privacyManifests": {
    "NSPrivacyAccessedAPITypes": [
      {
        "NSPrivacyAccessedAPIType": "NSPrivacyAccessedAPICategoryUserDefaults",
        "NSPrivacyAccessedAPITypeReasons": ["CA92.1"]
      }
    ]
  }
}

The guide also says "Apple does not correctly parse all the PrivacyInfo files included by static CocoaPods dependencies", so you may need to copy the required reasons from your libraries into your own config. It suggests looking for a PrivacyInfo.xcprivacy file in node_modules/package_name/ios. It says to update your Expo SDK libraries with npx expo install --fix. For a bare React Native app, it says to create the file in Xcode and add it to your iOS app target.

For Flutter, I did not find an official Flutter page on this, so check each plugin's release notes for a privacy manifest.

Check before you upload

  1. Update your SDKs and plugins to current versions.
  2. Build an archive with Product > Archive.
  3. In Xcode Organizer, open the context menu on the archive and choose "Generate Privacy Report". Apple's WWDC23 session on privacy manifests shows this and says the report is a PDF.
  4. Compare it with your App Privacy answers. The same session says to "Always refer to the Xcode privacy report when you are submitting your app to keep your Nutrition Label up to date." My post on the App Store product page covers those answers.
  5. Upload the build. Apple's page says an email follows if reasons are missing, and Expo's guide says it arrives within a few minutes of submitting.

Privacy gaps are one cause of rejection among many. For the rest, see common first App Store rejections.

A test plan for testers

Testers cannot see a manifest. But updating SDKs to fix it can break things that worked. So put the new build on TestFlight and ask for the main flows again: login, payments, push. For how to share the build, see TestFlight external testers and the public link. For the task itself, see how to write a test task. Paste-ready:

"This build has updated libraries. Open it on your iPhone. Sign in, then do the one thing the app is for. If there are payments, buy with the test account. Turn on notifications and tell me if one arrives. Tell me your iPhone model, your iOS version, and anything that crashed or looked different."

Where TestSwap fits

TestSwap is a free app testing exchange where makers test each other's apps. You post web, iOS and Android apps, with a link testers can open or install, like a TestFlight link or a Google Play testing link. You can add a test login that only signed-in testers see. Everyone starts with 3 credits. Writing a review earns 1, and each review your app receives costs 1. You can rate each review 👍 or 👎, and a 👎 takes back the reviewer's credit. TestSwap is not affiliated with Apple or Google.

Checklist

  1. My app has a PrivacyInfo.xcprivacy file in the target.
  2. It lists every required reason API category my code uses, with a reason that is true.
  3. I updated my SDKs and plugins before checking.
  4. I compared my SDKs with Apple's list.
  5. In Expo, I set ios.privacyManifests where a library needs it.
  6. I generated the privacy report from an archive and compared it with my App Privacy answers.
  7. I put the build on TestFlight and had testers run login, payments and push.

Questions or a fix I missed? Tell me (@dizid on X), or post your app on TestSwap.