Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Apple says a library in my app is missing a privacy manifest

Short answer

Apple introduced privacy manifests and SDK signatures so that each third-party library describes its own privacy practices. Apple keeps a list of SDKs that must include one, and the manifest must be present when you submit a new app that contains a listed SDK or an update that adds one. The usual fix is updating the library.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • An email or message from Apple says an SDK is missing a privacy manifest.
  • The upload was refused after a library was added or upgraded.
  • My developer says the message is about a library, not about our own code.
  • The same library is in other apps and nobody had trouble before.
  • The privacy labels on the listing are out of date and nobody knows what the libraries collect.

Why does this happen?

  1. Each SDK is expected to describe itself

    Apple states that a privacy manifest is a single, standard-format file describing the privacy practices of a third-party SDK's code. When you prepare to distribute an app, Xcode combines the manifests of all third-party SDKs in the app into one report, to help with accurate privacy labels.

  2. A published list decides which SDKs need one

    Apple's page lists the SDKs that require a privacy manifest. You must include the manifest when you submit a new app that contains a listed SDK, or an app update that adds a listed SDK. The requirement covers any version of a listed SDK, and SDKs that repackage them.

  3. Some libraries also need a signature

    The same page says signatures are required for listed SDKs used as binary dependencies. When a new version of an SDK is adopted, Xcode checks that it was signed by the same developer.

  4. The library in the app is an old copy

    Apps built years ago often keep running on old library versions, because nothing forced an upgrade. Adding a new feature that pulls in a listed SDK is when the old copy is noticed.

  5. Wrappers hide the real library

    In apps made with cross-platform tools, the listed SDK may sit underneath a plugin. The page says repackaged SDKs are covered too, so the plugin has to be updated, not just the visible library.

What can I do about it today?

  1. Save Apple's message and the name of the libraryCopy the full message. It normally names the library, and that name is what the developer needs.
  2. Ask whether a newer version existsAsk your developer if the library has a newer version that includes a manifest, and whether upgrading is safe for the features you use.
  3. Do not remove libraries to see what happensA library may carry payments, login or push notifications. Removing one blindly can break the app.
  4. Hold other changes until this shipsKeep the release small so that an unrelated change does not add a second problem.
  5. Check the privacy labels afterwardsAsk for a short list of what each library collects, and compare it with the answers in App Store Connect.

When should I bring someone in?

  • The library is no longer maintained and has no newer version.
  • The message names a library nobody can find in the code.
  • The update is urgent and the app is old enough that upgrading libraries breaks the build.

How do I handle it?

  1. Find every listed SDK in the buildI list the libraries inside the build, including those hidden under plugins, and compare the list with Apple's page.
  2. Upgrade or replaceEach library is moved to a version that includes the manifest, or replaced if it is abandoned, with a build and test pass after each change.
  3. Check the generated reportIn Xcode I generate the privacy report from the archive and read it, so that the declared practices match what the app actually does.
  4. Upload and confirm processingThe check is a build that uploads and processes cleanly in App Store Connect. Review itself is Apple's decision.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is the privacy manifest the same as my privacy policy?

No. The manifest is a file inside the app or the library. The privacy policy is a web page for customers. Apple's report from the manifests helps with the privacy labels.

Do I have to write the manifest myself?

For a listed third-party SDK, the library's maker supplies it, which is why upgrading the library is the usual fix.

Can I ask Apple for more time?

That is up to Apple and I cannot promise a result. It is usually faster to update the library.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.