-
Notifications
You must be signed in to change notification settings - Fork 66
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
Apple Sign in Issue #48
Comments
@guptahitesh121 I have similar problem but one step further. When user click the Sign in with Apple button in application it opens browser with auth0 tenant domain and then redirect to appleid.apple.com and the native login dialog is showing. I click the Continue button, then select email to share, click Continue with Password, entering password and hit enter. After a while the dialog disappears, my app login page shows and in the terminal I have got error with following call stack:
My code is:
And in the
And in
@guptahitesh121 I hope my code will help you some way. |
@mkolbusz This looks similar to the problem I am getting but I don't get any error in the console. Looking at the stack trace of the error that you are getting, it looks like the URL called by the platform is wrong may be it does not exist. Other than that I also don't have any clue. |
I am getting an issue in production with Apple sign in for that I am not sure if that is something this plugin can handle. So I ask for help to understand the issue.
The issue is when the user is logged in in iPhone settings with Apple id and then I try to login using auth0, it starts the browser and instantly browser gets closed by launching a native dialog to login with the same user or to switch to a different user. If user selects the same user then it does not go back to the browser to complete the login flow. Here I believe browser is the one which redirects the user back to our application using deep linking with a payload and, in this case, the native apple sign in dialog not going back to the browser. I guess this plugin looks for only browser to send back the idToken to our app.
So, in this case after apple sign in nothing happens, user sees the login screen of our app again. When there is no user in iPhone then the complete flow is managed by browser and login happens successfully. I think because of the native interface of Apple sign in which kicks in without our control, this flow is interrupted and at the end our app does not receive any payload from the Apple servers.
Can you please suggest what is the problem here or any solution for this?
The text was updated successfully, but these errors were encountered: