Why the sudden appearance of an invalid privacy manifest warning?

Question

Piepants OP

Created Sep ’24

Replies 2

Boosts 0

Participants 3

I just received a message upon app submission saying

"Although submission for App Store review was successful, you may want to correct the following issues in your next submission for App Store review. Invalid privacy manifest - The PrivacyInfo.xcprivacy file from the following path is invalid"

This is due to a 3rd party dependency being used by the app, but the thing is I was able to submit the app a few weeks ago, and a few months ago prior to that, and this warning wasn't present despite the exact same version of the 3rd party dependency being in those previous submissions as for the current submission.

As the deadline for including privacy manifests was earlier this year, and as the message says " you may want to correct the following issues in your next submission", then whats the point, is there any point in this message?

The wording doesn't even say must or should resubmit, it simply says "may like to". Is there therefore any need to address this or not bother if the message just says "may like to"?

Boost

Answer 1

darkpaw OP

Sep ’24

It's probably easier to correct the underlying issue by putting the privacy manifest in properly, then you won't see the error again.

0

Answer 2

DTS Engineer OP

Apple

Sep ’24

@Piepants,

From Adding a privacy manifest to your app or third-party SDK:

App submissions containing invalid privacy manifest files may be rejected.** If you upload an app to App Store Connect that contains privacy manifest files with unexpected keys or values, you’ll receive an email that includes the name and path of the invalid files in your app bundle**. Starting November 12, 2024, apps that don’t include a required privacy manifest can’t be submitted for review in App Store Connect. You’ll need to obtain and include in your app a valid version of all privacy manifest files mentioned in that email. If an invalid file comes from a third party SDK, contact its developer for an updated version of the SDK that includes a valid privacy manifest. Build, archive, and submit your app again using Xcode. For more information, see Distributing your app for beta testing and releases.

0