How German regulators are cracking down on App Tracking Transparency
Having rejected Apple's initial compromise proposals for App Tracking Transparency in the App Store , Germany says it has made a final agreement that will make the system fair to all developers. App Tracking Transparency Germany's federal cartel office, the Bundeskartellamt, has been challenging Apple over its App Tracking Transparency (ATT) feature. This is the feature that requires users to…
iOS rejected my iOS app under Guideline 2.1 due to a lack of visibility of the App Tracking Transparency permission request during testing. The prompt worked on my iPhone but not on the reviewer's device. The problem stemmed from two properties of the ATT API: iOS only presents the ATT prompt when the app is active, and iOS doesn't provide a clear indication when it declines to present the prompt, returning "notDeterminated" instead of an error or a specific signal.
This combination of factors led to a bug that was invisible on fast devices but reproducible on slow ones. The issue was compounded by treating "notDeterminated" as a final answer, rather than retrying, which prevented the prompt from ever appearing. The solution involved waiting for the app to reach an active state before requesting permission, implementing a timeout to prevent the issue from hanging the app, and retrying when the API returned "notDeterminated" instead of giving up.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
