Is ATT required for launching out to web?

My app was recently rejected because of non-compliance with App Tracking transparency because, while I do not use any kind of tracking in my app whatsoever, I do link out to the website that my company owns, and on that site, there are cookies.

I obviously cannot control what the website does as I'm not on that team. Is there any way to launch a website that uses cookies without requiring the ATT popup?

I've heard that SFSafariViewController is sufficient but WKWebview is not. Is this true? Is there something I can do to launch to the website (for things like FAQs) but avoid requiring the ATT popup?

Answered by tomquercia in 680678022

We eventually resolved this by launching out to Safari instead of using webviews inside our app.

Per this link:

https://developer.apple.com/app-store/user-privacy-and-data-use/

If tracking occurs within a webview inside an app, do I need to use the AppTrackingTransparency prompt?

Yes. If you are using a webview for app functionality, it should be treated the same way as native functionality in your app, unless you are enabling the user to navigate the open web.

So if you plan on using a webview to display the content inside your app, and that content uses cookies, you will need to display the ATT popup or you will be rejected.

We switched to launching out to Safari instead of keeping them in-app, and we were promptly approved, no need for ATT since our app was no longer able to track the user across sites or apps.

Hope that helps.

Hi, we're having the same issue, how did you manage it?

We are also in same situation - Can you provide some insights if you have resolved this !

Same issue here.. :(

Accepted Answer

We eventually resolved this by launching out to Safari instead of using webviews inside our app.

Per this link:

https://developer.apple.com/app-store/user-privacy-and-data-use/

If tracking occurs within a webview inside an app, do I need to use the AppTrackingTransparency prompt?

Yes. If you are using a webview for app functionality, it should be treated the same way as native functionality in your app, unless you are enabling the user to navigate the open web.

So if you plan on using a webview to display the content inside your app, and that content uses cookies, you will need to display the ATT popup or you will be rejected.

We switched to launching out to Safari instead of keeping them in-app, and we were promptly approved, no need for ATT since our app was no longer able to track the user across sites or apps.

Hope that helps.

I faced the same issue, so I implementented ATT in my app and fall back to launching Safari from the app.

That being said, it raise a question for me & ATT. To be fair, as a user, if I use Safari and visit any Apple website, shouldn't Safari ask me if I want Apple to track my activity on there website (they do use cookies). I mean, shouldn't the same rule apply for Apple?

I am using SFSafariViewController and the review teams still asked me to implement ATT. For the moment (still in review) I ask for ATT, and if I don't have the user consent I am replacing the Safari view by a message prompting the user to open the link externally.

Will tell you if the review team agree with me. For the moment, they disagree with the wording of the message in ATT.

I also had this problem and I am not sure what opening the URL with Safari improves. Using the SFSafariViewController you don't have access to any extra information that you would have when opening it from Safari. In addition, if I would like to track the user with some kind of identifier, I could send this identifier to Safari as well as a URL parameter. What is this measure trying to improve, apart from worsening the User Experience?

Some news ? my app is blocked, i have wkwebviews, even if i enter the ATT popup as i refuse to track a webview ? did you find a solution? unfortunately I can't redirect the user out of the app because the app is hybrid with webview operation

Is ATT required for launching out to web?
 
 
Q