Apple reject build because of ATT but ATT working as expected

Question

Created Nov ’22

Replies 2

Boosts 0

Views 2.5k

Participants 3

Hi,

Today Apple rejected our build because they said "We're looking forward to completing our review, but we need more information to continue. Your app uses the AppTrackingTransparency framework, but we are unable to locate the App Tracking Transparency permission request when reviewed on iOS 16.1.1.". But the problem is we didn't change anything approximately for the previous 20 builds and they were passing without problem.

Also we are testing with 4 different devices which versions are (15.6, 15.7, 16.1, 16.1.1) and on every device our ATT works as expected and showing ATT popup on the game beginning. Even though I have double checked with the documentation for ATT and send them video and screenshot from our test device which has the 16.1.1 version in it, they still didn't accept the build.

Is there anyone facing with this issue ?

Regards.

Boost

Answer 1

Claude31 OP

Nov ’22

But the problem is we didn't change anything approximately for the previous 20 builds

That's not an argument for reviewer. That may just mean this went unnoticed before, but not this time.

Question is:

Does our app use the AppTrackingTransparency framework ? I understand YES.
Can you locate in code where you ask for permission ?

Then you can simply give this information to reviewer, that should be enough.

Wish you good luck.

0

Answer 2

dylan153 OP

Feb ’24

@archengineer I have been facing this issue multiple times in the last 1.5 year.

A quick response to precise where the popup is located sometimes is enough, but not always.
Showing a screenshot or video recording may help, but not always.
Sometimes you don't know what to do.

It really is annoying, especially when you know you haven't changed any code related to this + they accepted previously + you know 100% that the popup is shown. There's an issue in my opinion in the reviewing of the ATT popup.

When I was using UIKit, it happened that I would request the ATT popup before the app had called applicationDidBecomeActive. This was kinda hidden because of Coordinators in place etc. I had opened a Code-Level Support TSI and the team in charge pointed me towards the proper thread in this forum, which was telling me about the _ applicationDidBecomeActive_

Today I am facing the issue again, but I am using a 100% SwiftUI application and I do request in .onAppear { } . I could have made the mistake to call it in .task { } but the latter may be called before the view is visible. I don't think I can do any better.

May Quinn the Eskimo come to the rescue. :prayer:

0