I have gotten past this problem. I'm afraid the answer isn't very enlightening. I think my configuration of the packages in the Unity Package Manager was just not correct. At least it seemed to just start working without doing any significant steps. I'm working with a plug-in Unity project that uses the Apple Unity Plugins. This plugin project is then referenced, by a Unity game project. I believe the issue was that the game project wasn't properly referencing the built tar packages. So now both the plugin project and game project are referencing the Apple Unity Plugin packages through pointing to their tarballs.

Thank you for the clarifying answer. Then indeed it looks like the released version is blocking the submission of new ones.

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?

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" grep NSUserTrackingUsageDescription -R ./ For us, some of our plugins are mentioning the string which might be flagged as use.

We are also experiencing this issue. Have you been able to alleviate it? If so, how did you do that?