App stuck in repeated 5.1.2 rejection because I can’t update incorrect “Device ID used for tracking” privacy label

App Store Distribution & Marketing App Review
nickkosty OP
Created 11h
Replies 1
Boosts 0
Views 111
Participants 2

Hi everyone,

I’m hoping someone can help because my app has been stuck in App Review since July 17, and I keep getting rejected under Guideline 5.1.2(i).

The issue is that my App Privacy information currently says Device ID is collected and used for tracking. However, the new version of the app does not track users as Apple defines tracking:

  • It does not access the IDFA.
  • It does not link against AppTrackingTransparency or AdSupport.
  • The new build does not contain NSUserTrackingUsageDescription in its Info.plist.
  • PostHog is used only for first-party product analytics.
  • Superwall is used for paywalls and subscriptions.
  • No collected data is linked with third-party data for advertising or shared with a data broker.

A previous version of the app included NSUserTrackingUsageDescription, but the new version does not. The problem is that App Store Connect is not allowing me to remove the “used for tracking” designation from the privacy information while the older version is still live/currently associated with the listing. Because that privacy label remains selected, App Review continues expecting an ATT permission prompt that the new app does not need.

I explained this in the Resolution Center and also requested approval under Apple’s Bug Fix Submissions policy, since version 3.0 (build 9) contains bug fixes. I have not received a response resolving the issue.

Each resubmission has taken close to a week to be reviewed, only to receive essentially the same rejection again. I also submitted an expedited review request, but the build still has not been reviewed. This process has now been going on since July 17.

Has anyone encountered this situation where an old version used NSUserTrackingUsageDescription, but App Store Connect would not allow the tracking privacy label to be corrected for a new version that no longer tracks?

What is the correct way to break this cycle?

  1. Is there a way to have Apple unlock the App Privacy section so I can remove “Device ID used for tracking”?
  2. Should App Review approve the new build after confirming that it does not access the IDFA or perform tracking?
  3. Is there another setting or declaration that must be changed before the new version can be approved?

Any help from an Apple engineer or another developer who has experienced this would be greatly appreciated.

Replies  1
Boosts  0
Views  111
Participants  2
DTS Engineer OP
Apple
8h

@nickkosty Thanks for your first post in the forums. This should be sent and address at the App Review team, on the email you should have received a link to contact them and I would suggest to do just that.

Is your current App Privacy label says "Tracking”? so they look for the AppTrackingTransparency prompt. When they don't see it, I guess is what you received a Guideline 5.1.2(i) rejection.

Meanwhile, App Store Connect is locking the App Privacy section because your binary still contains the NSUserTrackingUsageDescription or links to the tracking frameworks?

Is your privacy section is locked and will not allow you to remove the 'Tracking' designation? Even if you removed NSUserTrackingUsageDescription, a third-party SDK might still be silently linking the AdSupport.framework or AppTrackingTransparency.frameworks. What third party SDKs are you using?

Hope this helps. Wish you luck.

Albert  WWDR

App stuck in repeated 5.1.2 rejection because I can’t update incorrect “Device ID used for tracking” privacy label
First post date Last post date
 
 
Q