You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the openAuth method, and if the user has other browsers downloaded, they have an option to "Open in Chrome" for instance. For android, it seems like the task is continued and they are able to process the callback even if they move to another browser for the authentication. For IOS however, the process is detached so even if the deeplink goes back to the app, the flow that initiated the openAuth won't know that it has come back. Is there a way to detect this? Ideally this can be fixed by either allowing it to get back the deeplink params back into the app from the external browser or by blocking the authentication if they open up the browser instead of using our in app browser itself.
The text was updated successfully, but these errors were encountered:
When using the openAuth method, and if the user has other browsers downloaded, they have an option to "Open in Chrome" for instance. For android, it seems like the task is continued and they are able to process the callback even if they move to another browser for the authentication. For IOS however, the process is detached so even if the deeplink goes back to the app, the flow that initiated the openAuth won't know that it has come back. Is there a way to detect this? Ideally this can be fixed by either allowing it to get back the deeplink params back into the app from the external browser or by blocking the authentication if they open up the browser instead of using our in app browser itself.
The text was updated successfully, but these errors were encountered: