Hello, our Unity game (iOS/iPadOS) requests App Tracking Transparency on its first scene, before ads are initialized.
Background
App Review rejected an earlier build under Guideline 2.1(a) for a blank screen on iPad Air 11-inch (M3), iPadOS 27.0. In that build we called requestTrackingAuthorization right at launch and then waited until trackingAuthorizationStatus was no longer .notDetermined. The status never changed, so the app never left the first screen.
Current flow (this build was approved)
- Wait until
UIApplication.shared.applicationState == .activeand the app has focus. - Call
requestTrackingAuthorization(completionHandler:)once and wait for the completion handler. - If the completion returns
.notDetermined, wait about 4 seconds while the app stays active, then call it one more time. - Wait until the status is no longer
.notDeterminedbefore loading the next scene. There is no timeout.
The first scene runs on every cold launch, so if the status is still .notDetermined, the request is made again on the next launch.
[ATTrackingManager requestTrackingAuthorizationWithCompletionHandler:^(ATTrackingManagerAuthorizationStatus status) {
dispatch_async(dispatch_get_main_queue(), ^{
// store status; Unity polls it on the main thread
});
}];
We have not been able to reproduce the original problem on our own devices.
Questions for those who have shipped apps with ATT
- How many times do you retry
requestTrackingAuthorization, and how long do you wait between attempts? Is there any limit you know of? - If the status still stays
.notDeterminedafter retrying, do you let the user continue and treat it as not authorized (no IDFA), or keep waiting? If you wait, how long before you let the user continue? - If you continue without tracking, did App Review ever flag that?
Any experience or pointers to documentation would be appreciated.