-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS: Configuring the associated domain does not work for custom domains #430
Comments
I am also facing the same issue, Any updates? @Widcket |
Just use old version of auth0_flutter
|
I am having this same issue using the latest version of the Auth0 Swift SDK. Associated Domain does not work with the default Auth0 tenant domain or with a custom domain. Same steps to reproduce as OP, same error as OP. Any word on a fix @Widcket ? I will look into downgrading versions but I don't love that as a long term solution |
This most likely means you ran the app before completing the SDK integration steps (before fulfilling all the requirements for the associated domain), and now Apple's CDN will have the wrong AASA file cached. You can check by making a get request to |
Note that for debugging purposes, you can attach any query parameter to the CDN URL, and it will cause the CDN to bypass the cached version and fetch the current AASA file (but it will not be persisted). E.g. |
@Widcket I checked the AASA file and it looked correct to me. The only curious thing was that the applinks object was populated as well as the webcredentials object, but I am only using the webcredentials for associated domain in Xcode. I also tried downgrading versions as suggested for the flutter SDK earlier in this thread with no luck. I am going to start from the beginning on a different Auth0 tenant and post the results. I will also try setting up a custom url scheme instead of the default to see if that works |
This sounds like a bug with auth0 SDK. It started working for me after I added both the custom domain and the auth0 domain in the App.entitlements file.
|
I agree with @freesuraj. It worked for me if I used the Auth0 domain in the Auth0 initialization and in the .entitlements file instead of a custom domain. @Widcket It looks like Auth0 only added the apple-app-site-association file for the Auth0 domain. When I tried |
Checklist
Description
I followed the instructions in the README.md for iOS/macOS: Configure the associated domain and I was able to get the login and logout functions that use the
useHTTPS: true
property to work with the auth0 domain but not a custom domain.I get this error when using the custom domain:
An unexpected error occurred. CAUSE: Error Domain=com.apple.AuthenticationServices.WebAuthenticationSession Code=1 "Application with identifier {YOUR_BUNDLE_ID} is not associated with domain {YOUR_CUSTOM_DOMAIN}. Using HTTPS callbacks requires Associated Domains using the 'webcredentials' service type for {YOUR_CUSTOM_DOMAIN}." UserInfo={NSLocalizedFailureReason=Application with identifier {YOUR_BUNDLE_ID} is not associated with domain {YOUR_CUSTOM_DOMAIN}. Using HTTPS callbacks requires Associated Domains using the 'webcredentials' service type for {YOUR_CUSTOM_DOMAIN}.}
Reproduction
Follow the instructions in the README.md for iOS/macOS: Configure the associated domain and use a custom domain instead of the auth0 domain. Make sure the Auth0 SDK is initialized with the custom domain.
Use the login and logout functions to see the error.
I ran the application on an iOS simulator version iOS 17.4+.
Additional context
No response
auth0_flutter version
1.6.0
Flutter version
3.19.3
Platform
iOS
Platform version(s)
No response
The text was updated successfully, but these errors were encountered: