We utilize universal links for our auth flows through Safari. What we are seeing is when the user selects the "username and password" stored in the keychain, the form gets autofilled and sometimes autosubmitted. When this occurs the method application:continueUserActivity:restorationHandler in the application's AppDelegate does not get triggered, leaving the user stuck on Safari.
Did you resolve your issue? We have a similar problem
...
We also have the same issue, has anyone found a solution or even a cause for this? We noticed that the "autosubmit" only happens the first time the user visits the safari sign in page, if the user revisits the page, the auto submit is not occurring and the user can press the login button, which works (the user is redirected to the app as expected).
After a few minutes, if the user visits the page again, the form goes back to autosubmit (initially), until the user visits the page again. Very strange.
Same issue here, anybody has workaround for this?
Same problem here.
Same issue here.
Sam issue here
Same issue.
Interesting thing that it is the same for SSO, actually we have started researching why the universal link was not working after the SSO login, and ended up here, since we have noticed the same behavior for the login with an autofilled passwords.
It might be related to the iOS trying to figure out the user’s intent (either to continue in a Browser, or to open an App), since in both SSO and autofilled password scenarios the user does not have to click on a, say, login button. I am not sure how the iOS technically could be tracking that, though.
Please share if you have got any ideas.