Thanks for being a part of WWDC25!

How did we do? We’d love to know your thoughts on this year’s conference. Take the survey here

App Transparency can't publish for review?

Hi recent app update review was rejected because we were informed we had to implement the App Transparency Tracking UI to let users choose. (we had just successfully published two days prior to this, and we need to get some bug fixes out with a new submission)

Nothing about the app with respect to data collection had changed between the successful submission and the rejection and still wondering why we were rejected for that reason.

We do not track data. We do collect user info and info about app usage for user account login and app performance analytics, and also for our development cycle.

So I updated the app to present the Tracking Transparency UI at startup and that is all good.

Now I add the app to the submission form, and I go update our privacy policy to define what data we collect and how we are using it. I publish the updated privacy information.

but now I am stuck. The submission page returns a message that I have to set up the privacy data to be able to submit for review

Your app contains NSUserTrackingUsageDescription, indicating that it may request permission to track users. To submit for review, update your App Privacy response to indicate that data collected from this app will be used for tracking purposes, or update your app binary and upload a new build. Learn More

But I have already defined and published that privacy data. It seems it is not finding the Privacy data or what?

What could be going wrong here?

Thanks for any ideas!

Answered by GordonL in 829328022

yes, our policy was in there.

I figured out the problem. IF you collect data but do not indicate that you are actually tracking it, it doesn't let you submit for review.

I have no idea why you can select the options for collecting data for app performance and development and that is not good enough to pass for the use of ATT.

Again we were forced to implement ATT by a rejected submission when exactly the same app, sans two minor bug fixes, passed the review 2 days earlier without ATT.

It's like the reviewers had different standards. We've passed submission through over 30 updates with this up until this one that failed 2 days ago, and with respect to data collection nothing had changed.

So I had to set one of the data definitions to the option that states we are tracking it in addition to mere data collection.

Thanks for your response!

Have you updated the info on this page in App Store Connect?

And, does your app have the right info in the .xcprivacy file?

Accepted Answer

yes, our policy was in there.

I figured out the problem. IF you collect data but do not indicate that you are actually tracking it, it doesn't let you submit for review.

I have no idea why you can select the options for collecting data for app performance and development and that is not good enough to pass for the use of ATT.

Again we were forced to implement ATT by a rejected submission when exactly the same app, sans two minor bug fixes, passed the review 2 days earlier without ATT.

It's like the reviewers had different standards. We've passed submission through over 30 updates with this up until this one that failed 2 days ago, and with respect to data collection nothing had changed.

So I had to set one of the data definitions to the option that states we are tracking it in addition to mere data collection.

Thanks for your response!

App Transparency can't publish for review?
 
 
Q