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
I am simulating some connectivity issues like no internet connection and 100% packet loss in our iOS app, however I am not getting any callback from acquireToken method when facing these issues after credentials have been granted and the app remains in infinite loading.
I only had this problem after the pages were fully loaded, when I start loading these pages without an internet connection for example, I receive the callback normally. I tried some workarounds to track down these scenarios, like overriding the navigationDelegate property of the custom WebView we are using, but I got some assertion errors.
Is there any configuration that impacts this behavior or can I set a timeout for the authentication process?
The text was updated successfully, but these errors were encountered:
@vitor-desouza Could you elaborate your use case? I'm assuming you are calling to acquire token interactively. In your simulation at what point are you killing the internet connection?
Hi team,
I am simulating some connectivity issues like no internet connection and 100% packet loss in our iOS app, however I am not getting any callback from acquireToken method when facing these issues after credentials have been granted and the app remains in infinite loading.
I only had this problem after the pages were fully loaded, when I start loading these pages without an internet connection for example, I receive the callback normally. I tried some workarounds to track down these scenarios, like overriding the navigationDelegate property of the custom WebView we are using, but I got some assertion errors.
Is there any configuration that impacts this behavior or can I set a timeout for the authentication process?
The text was updated successfully, but these errors were encountered: