[Bug]: ITMS-91064: Invalid tracking information

[kshrikant]

Platform

iOS

Platform Version

iOS 18

Braze SDK Version

11.3.0

Xcode Version

XCode 16

Computer Processor

Apple (M1)

Repro Rate

100

Steps To Reproduce

While build upload its giving error -

Expected Behavior

Build should upload without error.

Actual Incorrect Behavior

Please correct the following issues and upload a new binary to App Store Connect.

ITMS-91064: Invalid tracking information - A PrivacyInfo.xcprivacy file contains invalid tracking information at the following path: “BrazeKit.bundle/PrivacyInfo.xcprivacy”. NSPrivacyTracking must be true if NSPrivacyTrackingDomains isn’t empty. Keys and values in your app’s privacy manifests must be valid. For more details about privacy manifest files, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files.

Apple Developer Relations

Verbose Logs

No response

Additional Information

No response

[kshrikant]

@lowip @jerielng @hokstuff could you please help me to resolve this ?

[jerielng]

Hey @kshrikant, could you verify the version you are using? This should be resolved in the latest, or any version 9.0.0 or greater.

[kshrikant]

Hey @kshrikant, could you verify the version you are using? This should be resolved in the latest, or any version 9.0.0 or greater.

yes, as i said its 11.3.0

[jerielng]

@kshrikant Could you write into support@braze.com with further details of your project, including:

• whether you are using static or dynamic frameworks
• whether you are using strictly the Braze Swift SDK, or a hybrid wrapper SDK (like React Native or Flutter, for example)
• a copy of your Podfile
• a copy of the BrazeKit privacy manifest that's bundled in your upload binary

In your email, reference this GitHub issue, and our support team will be able to dive in deeper to diagnose this. Thanks!

[kshrikant]

@jerielng We are using static framework by installing 11.3.0 version.

I got this latest update from Apple -

https://developer.apple.com/documentation/bundleresources/adding-a-privacy-manifest-to-your-app-or-third-party-sdk

From Nov 12 2024 there is update about the structuring the path -

PrivacyInfo.xcprivacy at SampleFramework.framework/PrivacyInfo.xcprivacy:

But for Brazekit I can see the path is little different for reference -

Could you please check this once and let me know ?

[jerielng]

@kshrikant At the moment, we don't have reason to believe that the path is incorrect since the email you shared was able to successfully detect the location of the privacy manifest. The error message in that email indicates an issue that was resolved in 9.0.0, where we removed the URLs from the list of tracking domains. If you are able to write in to our support team, we should be able to dive deeper into this to understand the issue further.

[envisean]

Any update to this? I am dealing with the same thing on our latest build as I'm submitting it to Apple App Store

[lowip]

Hi everyone,

Some context

• This issue exists only when integrating the static versions of our XCFrameworks, which includes the XCFramework distributed by the two repositories:
  • https://github.com/braze-inc/braze-swift-sdk
  • https://github.com/braze-inc/braze-swift-sdk-prebuilt-static
• With the release of Xcode 15, Apple has added first-party support for resources in static XCFrameworks.
  • Until then, resources included in the static XCFramework would not be copied into your final .ipa / .app package.
  • We provide additional resources-only targets in our Package.swift as a workaround for this limitation, which are automatically included as part of the distributed product (e.g., BrazeKitResources).
  • Unfortunately, our testing revealed that Apple's implementation of resources in static XCFrameworks was not working as expected in all contexts until Xcode 15.3. Specifically, static XCFrameworks distributed via SwiftPM do not copy their resources into the final .ipa / .app package until Xcode 15.3.
  • The PrivacyInfo.xcprivacy is one of these resources.
• Braze strives to support as many integrations as possible, remaining as close as possible to what is allowed to be distributed on the App Store. At the time of this comment, the App Store requires using Xcode 15.0+ and iOS 12+, while Braze requires using Xcode 15.2+ and iOS 12+.
  • Apple updates those requirements every year ahead of WWDC (around end of April — i.e., last year's announcement).
  • We cannot upgrade our own requirements until Apple forces each of our clients to upgrade their Xcode version.
• This App Store warning will disappear once we are able to distribute our static XCFrameworks with more recent versions of Xcode.
  • This new requirement will ensure that all of our clients use versions of Xcode that fully support resources in static XCFrameworks.

Workaround

For the time being, the easiest way to avoid this warning is to integrate the dynamic variant of our SDK: https://github.com/braze-inc/braze-swift-sdk-prebuilt-dynamic

We will make sure to update this thread once the situation with our distributed static XCFrameworks is resolved, most likely at the end of April / beginning of May of this year.

[envisean]

Hi @lowip we're using braze w/ react-native, based on the link you provided, is the fix as simple as just adding in the 2 lines for the Podfile?

We are using @braze/react-native-sdk@^9.0.0

[envisean]

@lowip ok, it's not just a warning from Apple, they won't allow us to release the software. I tried switching this w/ the dynamic library, and apparently we already had our own PrivacyInfo file at the top level of the project. I'm not sure what changed here recently, but builds even a month ago were perfectly fine with the App Store. I emailed the support team as well, but haven't heard back.

[lowip]

Hi @envisean, please update @braze/react-native-sdk to at minimum 10.0.0. The version of the underlying Swift SDK you are currently running does not includes the finalized version of our privacy manifests.

[lowip]

Hi everyone,

I'm closing this thread, we have released the Braze Swift SDK 12.0.0 which fixes the issue.

Best,