Can not update your app privacy information about tracking user

2023-10-20 This problem still there

2024-02-10 Still not resolved. Once your want to remove APP PRIVACY settings to indicate that you stopped tracking users or collecting data the PUBLISH BUTTON on APP PRIVACY form gets disabled. There is a message that your build uses "NSUserTracking..." permission, but this permission was removed in the latest build that we are trying to get approved. The info about the permission is connected to the version released on APP STORE not to the build that we are trying to upload. So you can never change APP PRIVACY settings if your build is not released first. The only solution is: You must approve our build and only then we will be able to update the privacy form.

I have read all the responses on this, thought my process would take a long time. I was finally able to resolve this issue.

1. I published an update where I removed all the ads and NSUserTrackingUsageDescription. I also removed all mention of it in my code.
2. Uploaded a new version which successfully passed moderation.
3. Only then did I update the App Privacy. A miracle happened, my app no longer contains ads and everything displays correctly.

Rejected three times in a row under Guideline 2.1 for "using the AppTrackingTransparency framework" despite zero tracking code or frameworks anywhere in the binary. Verified at every level before each resubmission:

• otool -L on the main executable: only Apple system frameworks, no AppTrackingTransparency, no AdSupport, nothing third-party
• Frameworks/ folder in the compiled .app bundle: completely empty
• No .appex extensions
• PrivacyInfo.xcprivacy: NSPrivacyTracking = false
• No source file imports AppTrackingTransparency or calls ATTrackingManager
• App Privacy in App Store Connect already set to "No" for tracking

This matches exactly what's described above — the app previously had ads requiring tracking, removed everything for the new version, but the rejection keeps citing the old declaration tied to the currently live build.

@khlebobul's solution (publish removal first, only then update App Privacy) makes sense in theory, but in our case the rejection itself is what's blocking that "publish" step — can't get the cleaned build approved to begin with because reviewers keep citing the stale tracking reference.

Anyone gotten an actual response from an Apple engineer on this thread, or only the same canned rejection message regardless of binary evidence submitted?