This is early days for this question, but having just gone through a rejection with Apple I am wondering whether anybody may have any feedback available with regards to the relationship between WKWebView, WKAppBoundDomains and App Tracking Transparency.
So these days even the simplest site uses cookies. They are not necessarily for "tracking" users or advertising, but can be used for a range of things from remembering user preferences across sessions to passwordless logins across sessions and everything that falls inbetween.
So, for the needs of the "App Tracking Transparency", just what is the definition of "Tracks user data"? is setting of cookies that persist across sessions considered "tracking"? Will the age of cookies make a difference? Is there a requirement to - for example - clear cookies if the user "Asks not to track"?
Further, does the use of WKAppBoundDomains remove the necessity for ATT Prompt? (Assuming the rest of the app does not use the IDFA and cookies are not cross-domain, and nothing else nefarious is going on). We can always pop links to other domains that sneak up to open in Safari.
And lastly, what are the options for a WKWebView when the users, (inevitably suffering from permission fatigue), disables the ability to ask, and denies everything by default?
If anybody has any answers, they would be much appreciated. TA
Serg