Thanks for the update @chad.timmerman; glad to hear you’ve got things working and a great suggestion for folks to double-check too
Folks, I wanted to bring you some update on the progress of this. We’re still trying to pinpoint what may be the exact cause, however, something that Apple shared relatively recently was that the situation may well be improved with iOS 18: Bug: AASA file not fetched on app … | Apple Developer Forums. As iOS 18 is now GA, it would be great if anyone has any experience either way that they can share. Thank you
Hi Peter,
I’m having the same issue, simulator on 17.4 - fails, downgrade to 17.2 - suceeds, upgrade to 18.2 - suceeds, which is great for the future, but for now the bulk of users are on 17.4+ so I was wondering if there is a workaround ?
Also just to amend my previous comment, I looked up statistics, and for me, in Australia, a suprisingly high amount of people are on ios 18… so maybe it’s not such a big deal. Also just wanted to let you know 17.4 doesn’t matter if it’s simulator or device. Thank you!
Is there any update on this topic? I saw a similar one posted as well, but it was closed. My iOS app gets rejected about half the time from App Store review since the reviewer is unable to login. The exchange fails when Auth0 is trying to fetch the Apple App Site Association file. I can tell based upon the logs that I see after the review fails. I implemented a retry mechanism, but this doesn’t work consistently.
The reviewer is using the following:
- Device type: iPhone 13 mini and iPad Air (5th generation)
- OS version: iOS 18.3.1
Hi all,
Thank you for your continued patience on this one! Please see the below response from our Engineering team:
Since the issues from a few different customers have been brought up, let’s distinguish those experiencing the following:
-
The issue seems to happen only when attempting a login/registration really fast after a fresh install of the app
-
If the user waits a few seconds, the issue does not happen
If your issue falls into the above scenario, please be aware that an Apple engineer has acknowledged the existence of an iOS bug regarding the verification of the Associated Domain. It should be fixed on iOS 18. See Bug: AASA file not fetched on app … | Apple Developer Forums
Please see if updating to iOS 18 solves your issue.
If your issue does NOT fall into the above scenario, it’s likely a matter of configuration/setup. Please make sure you:
- Have correctly set up the Associated Domain as described in GitHub - auth0/Auth0.swift: Auth0 SDK for Apple platforms
- If you’re using a custom domain, you have correctly set it up, both in the Auth0 dashboard and in the SDK configuration/setup.
- Are able to get it to work using the Auth0.swift sample app, as it’s been verified to work by us during the development of Auth0.swift 2.6.0. If you 1) are getting the error on the sample app and 2) it’s not the iOS bug scenario described above, it’s very likely to be either a configuration/setup issue, or the caching/Xcode debugging issue described here.
After you’ve verified all of the above, please confirm if the issue persists.
Thanks,
Mary Beth
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.