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?
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags: