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
Hi everyone, some users are experiencing an issue with the login if they dismissed it by tapping outside the view controller (if they tap in the cancel button there is no problem)
We have a "Log in" button that calls the following code
Then the salesforce login is presented in a modal which works fine, but if the user taps outside the modal the login modal is dismissed and there is no way of presenting the login view again
I thought that maybe canceling the cancelable would help but it didn't
@auctifera-josed - I did try to capture the tap outside the login form gesture, but didn't succeed. Seems to be a limitation of Apple's prescribed authentication mechanism using ASWebAuthenticationSession.
Another idea I had but haven't had time yet to prototype: Salesforce allows you to specify a different form factor for the login form - see the display parameter at this link. Swiftly Salesforce currently uses touch -- maybe page offers a larger display which, if accommodated by ASWebAuthenticationSession, would make it less likely that the user clicks outside the bounds of the login form?
Hi everyone, some users are experiencing an issue with the login if they dismissed it by tapping outside the view controller (if they tap in the cancel button there is no problem)
We have a "Log in" button that calls the following code
Then the salesforce login is presented in a modal which works fine, but if the user taps outside the modal the login modal is dismissed and there is no way of presenting the login view again
I thought that maybe canceling the cancelable would help but it didn't
Even tried reinitializing the
salesforce
property before calling theidentity
Does anyone have an idea what's going on here? Or maybe just how can we present the login modal in full screen so they can't tap outside?
The text was updated successfully, but these errors were encountered: