ASWebAuthenticationSession cookie

Failed to access iCloud data I'm also experiencing this issue, after turning on advanced data protection I'm almost always unable to access the containers with the same error show in the OP's screenshot. Attempted Resolution signing out and signing back in does not resolve additionally turning Advanced Data Protection on or off does not resolve. attempts on multiple devices (mac, iphone) and browsers (firefox, chrome, safari) do not resolve clearing browser cache and cookies does not resolve VERY occasionally (like literally once a week,) I am able to sign in following normal sign on procedures and view the private and shared containers of a production or development environment. Its really frustrating! What's going wrong Here's a screenshot of the browser's console on a failed attempt to view the private container, not sure if helpful:

well, that lasted two minutes. firefox udate fixed the problem, then i closed firefox to clear cache & cookies (from this site) and reopened. now it’s junk again. thanks, apple! and thanks for all your help here! it's amazing, the number of helpful responses!

well, that lasted two minutes. closed firefox to clear cache & cookies and reopened. now it’s junk again. thanks, apple!

We have the same issue, and it's very annoying. We rely on Universal Links for login (for secure callback from ASWebAuthenticationSession to the app), so App Review definitely stumble upon that issue during review. We never get any user tickets about it and it never occurs during our own testing, but it happens pretty often during App Review. So far, luckily, we have explained the situation to App Review, they try again, and it works. But it feels very fragile; there must be something with the App Review install process which is not reliably registering Universal Links.

@garrett-davidson Sure thing. I do think some of our users will be confused, but that is also partly due to the login provider my company uses and decisions I don't have much control over. When users are presented this choice, I expect them to choose app only, and I don't blame them. The problem we'll face is that a remember my device setting for MFA is cookie-based, and users will be unintentionally disabling that. So we'll either have to communicate that to them pro actively or handle it on the support side. When I first saw this, I was actually excited because I thought it was going to help me make the case for dropping our login provider in favor of something more user friendly. But that's realistically a bit of a stretch and I expect many in a similar situation will just be stuck supporting it. In terms of improving this feature, one pain point with these SSO type logins is that you also get the prompt asking for permission to sign in when a user signs out, if you actually want to clear out the

Using WebAuthn (i.e. security keys or passkeys) is only supported for first-party uses in WKWebView. For third-party sign in (e.g. Sign in with Apple), you'll need to use ASWebAuthenticationSession.