Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Xcode archive or upload says there is no privacy manifest

ErrorArchive does not contain any PrivacyInfo.xcprivacy files

Short answer

Your app target does not contain a PrivacyInfo.xcprivacy file, or the file is there but is not packaged into the product. Create it with the App Privacy File template, tick your target, declare any required reason APIs, and make sure Swift package and SDK manifests are copied as resources. Then archive again.

  • Applies to Xcode 16, Xcode 26, iOS 18
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Look inside the archive. List every privacy manifest that was actually packaged, for the app and for each framework.

    find ~/Library/Developer/Xcode/Archives -name "PrivacyInfo.xcprivacy" -path "*MyApp*" | head
  2. 2Match what you see, then jump to its fix

    1. 1The find command above returns nothing for your app, and no PrivacyInfo.xcprivacy sits in the Project navigatorThe app target has no privacy manifest at allFix
    2. 2Apple's mail or the upload log says an API is used without a declared reason, even though a manifest file existsYour code uses a required reason API but declares no reasonFix
    3. 3The app manifest is in the archive but a framework or package has none, or App Store Connect names an invalid manifest pathAn SDK or Swift package ships a manifest that is not packaged or not validFix

What does the error look like?

  • Archive does not contain any PrivacyInfo.xcprivacy files

Cause 1 of 3

The app target has no privacy manifest at all

1Check

Search the project folder for the file, and check that it is ticked for the app target in the File inspector.

find . -name PrivacyInfo.xcprivacy -not -path './Pods/*' -not -path './build/*'

2Fix

In Xcode choose File > New > File, pick App Privacy File under Resource, tick your app target and click Create. Keep the default name PrivacyInfo.xcprivacy: Apple calls it the required file name for bundled manifests.

# Minimum valid content, then fill in what your app really does
<dict>
    <key>NSPrivacyTracking</key><false/>
    <key>NSPrivacyTrackingDomains</key><array/>
    <key>NSPrivacyCollectedDataTypes</key><array/>
    <key>NSPrivacyAccessedAPITypes</key><array/>
</dict>

3Verify

Archive again and run the find command from the first step. The app's manifest now shows up.

find ~/Library/Developer/Xcode/Archives -name "PrivacyInfo.xcprivacy" -path "*MyApp*" | head

Confirmed by developer.apple.com

Did this fix it?

Cause 2 of 3

Your code uses a required reason API but declares no reason

1Check

Required reason APIs must be declared in the manifest of the bundle whose code calls them. An empty NSPrivacyAccessedAPITypes array declares nothing.

plutil -p MyApp/PrivacyInfo.xcprivacy

2Fix

Add one dictionary per API category to NSPrivacyAccessedAPITypes with NSPrivacyAccessedAPIType and an NSPrivacyAccessedAPITypeReasons array. Take the category and reason codes from Apple's list, and only pick a reason that matches what the app does. An SDK's own code is declared in the SDK's manifest, not yours.

<key>NSPrivacyAccessedAPITypes</key>
<array>
    <dict>
        <key>NSPrivacyAccessedAPIType</key>
        <string>CATEGORY_FROM_APPLE_LIST</string>
        <key>NSPrivacyAccessedAPITypeReasons</key>
        <array><string>REASON_CODE_FROM_APPLE_LIST</string></array>
    </dict>
</array>

3Verify

Check the file is still valid XML plist, then upload again.

plutil -lint MyApp/PrivacyInfo.xcprivacy

Confirmed by developer.apple.com

Did this fix it?

Cause 3 of 3

An SDK or Swift package ships a manifest that is not packaged or not valid

1Check

For a Swift package, the manifest must be declared as a resource. Static libraries cannot carry resources. XCFrameworks need a manifest in every platform slice.

find ~/Library/Developer/Xcode/Archives -path "*Frameworks*" -name PrivacyInfo.xcprivacy
plutil -lint path/to/SDK/PrivacyInfo.xcprivacy

2Fix

In your own package, add the file to the target folder and declare it with .process in Package.swift. For a static library, ship it as a static framework bundle that includes the manifest. For a third-party SDK with an invalid manifest, ask the vendor for a fixed release.

.target(
    name: "SomeLibrary",
    resources: [.process("PrivacyInfo.xcprivacy")]
)

3Verify

Archive and confirm the package's bundle now contains the manifest.

find ~/Library/Developer/Xcode/Archives -name PrivacyInfo.xcprivacy | wc -l

Confirmed by developer.apple.com

Did this fix it?

How do I stop it coming back?

  • Keep PrivacyInfo.xcprivacy in source control next to Info.plist and tick the target when you add it.
  • Run plutil -lint on every manifest in CI, because App Store Connect rejects invalid ones.
  • When you add an SDK, check that its release contains a manifest before you ship.
  • Re-read your reason codes whenever you start using a new system API.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Related fixes

Mobile apps

App record creation fails because you lack permission

You cannot add a new app in App Store Connect as a Developer or limited user

Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.