Can not update your app privacy information about tracking user

Can not update app privacy information about tracking user after remove the tracking functionality and "NSUserTrackingUsageDescription" from info.plist. Always reminds us App contains "NSUserTrackingUsageDescription"
Post not yet marked as solved Up vote post of X-LYing Down vote post of X-LYing
9.8k views
Posted by
X-LYing
Reply
Add a Comment

Replies

Same here....
Posted by
gatelli
Post not yet marked as solved Up vote reply of gatelli Down vote reply of gatelli
Add a Comment
We are also experiencing this issue. Have you been able to alleviate it? If so, how did you do that?
Posted by
guise
Post not yet marked as solved Up vote reply of guise Down vote reply of guise
Add a Comment
Same issue for me, no solution are provided for now by the support...
Posted by
gnoumaster
Up vote reply of gnoumaster Down vote reply of gnoumaster
Add a Comment
Same here... any news?
Posted by
r-developer
Up vote reply of r-developer Down vote reply of r-developer
Add a Comment
After doing some digging it might not be the Info.plist that is the issue.

Try running this in your project folder to search all files for the string "NSUserTrackingUsageDescription"
Code Block 
grep NSUserTrackingUsageDescription -R ./


For us, some of our plugins are mentioning the string which might be flagged as use.
Posted by
guise
Up vote reply of guise Down vote reply of guise
Add a Comment
You're right, but I guess that there is also a bug inside AppStore Connect, the NSUserTrackingUsageDescription reminder occurs even if your submitted code doesn't contain it : alert may come from the released version and not the submitted one.
Posted by
gatelli
Up vote reply of gatelli Down vote reply of gatelli
Add a Comment
Same here, App Store checks submitted version but not that was uploaded
Posted by
Vadimkoz
Post not yet marked as solved Up vote reply of Vadimkoz Down vote reply of Vadimkoz
Add a Comment
We also theorize that is what is happening because we removed it from the plist, and still could not update the app privacy information. Though, we have not been able to confirm that the released version is the issue since removing any reference to the NSUserTrackingUsageDescription turned out to be more work than anticipated.

Has anyone else been able to confirm this by uploading a version where no piece of the code references the NSUserTrackingUsageDescription?
Posted by
guise
Up vote reply of guise Down vote reply of guise
Add a Comment
my code doesn't contain any reference as follow.
Code Block 
grep -r ASIdentifierManager .
grep -r AdSupport.framework .
grep -r advertisingIdentifier .
grep -r NSUserTrackingUsageDescription .

Posted by
gatelli
Post not yet marked as solved Up vote reply of gatelli Down vote reply of gatelli
Add a Comment
Thank you for the clarifying answer.

Then indeed it looks like the released version is blocking the submission of new ones.
Posted by
guise
Up vote reply of guise Down vote reply of guise
Add a Comment
Same issue here
Posted by
Pitetou
Up vote reply of Pitetou Down vote reply of Pitetou
Add a Comment
Same exact problem. My app is developer jail after trying to get rid of admob and there seems to be no escape. I removed the NSUserTrackingUsageDescription and tried again to remove this from the user privacy settings. It still did not work.
Posted by
DVDxDV
Up vote reply of DVDxDV Down vote reply of DVDxDV
Add a Comment
Someone has solved the problem？Help！
Posted by
xida2021
Up vote reply of xida2021 Down vote reply of xida2021
Add a Comment
Nope. Apple is aware of this, but I don't know yet if it's Apple side or app side. You should submit a request to Apple assistance.
Posted by
gatelli
Up vote reply of gatelli Down vote reply of gatelli
Add a Comment
I'm having the same issue. I tried as many combinations as possible in the privacy section. Maybe that would enable my publish button. No luck. Went to the extent of asking my developer to remove altogether the NSUserTrackingUsageDescription key from our app's plist and submit a new binary. Still, the same message. Contacted the Apple revision team. They are unable to provide clear guidance. If anyone has a solution... PLEASE!
Posted by
Constantinvs
Up vote reply of Constantinvs Down vote reply of Constantinvs
Add a Comment