My team is currently experiencing some undesired behavior during the Sign in with Apple auth flow.
When the user is on the last screen on the appleid.apple.com auth page: Sign in with Apple ID
They are presented with two options, cancel or continue. If the user clicks continue once and waits, they are logged in successfully, however if the user clicks the continue button twice in a row auth0 redirects the user to the error page with the following error:
“You may have pressed the back button, refreshed during login, opened too many login dialogs, or there is some issue with cookies, since we couldn’t find your session. Try logging in again from the application and if the problem persists please contact the administrator.”
Additionally, this error in the auth0 logs shows up as Failed Login with N/A for the connection and Application.
What is even more puzzling is this behavior seems to only impact Safari and Chrome. In Firefox the user can click the continue button multiple times and is still logged in successfully.
+1 on the issue. Clicking twice on the continue button in the app login page causes a redirect to error page.
The message says: invalid_request : You may have pressed the back button, refreshed during login, opened too many login dialogs, or there is some issue with cookies, since we couldn’t find your session. Try logging in again from the application and if the problem persists please contact the administrator.
Hey Konrad, Please feel free to reach out to me and I can help you access an environment to reproduce this issue. Just don’t want to share URLs and usernames publicly… Thanks!
We are still seeing this issue. It happens with the iOS autofill of the 2FA password - for some reason it seems apple’s autofill “double clicks” the continue button.
Is there a way Auth0 can update that button so if its double clicked by accident or by autofill, it does not throw this error?
When WCAG accessibility feature is turned on, the universal login page no longer disables submission after the first click, so its still broken with that flow. I hope this will be resolved before the WCAG feature is forced enabled on everyone’s tenants in February 2025.