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
In our apps we call the method restorePreviousSignInWithCallback: every startup. This is recommended by the documentation, and we do this in order to be informed that the user's token was revoked. restorePreviousSignInWithCallback: can fail for many reasons, for example if there was a failure to refresh the token. In most of these cases, we would still like to get the cached token, even if it expired or about to expire. However currently there is no way to get the token if an error occurred during restorePreviousSignInWithCallback:.
In our apps we call the method
restorePreviousSignInWithCallback:
every startup. This is recommended by the documentation, and we do this in order to be informed that the user's token was revoked.restorePreviousSignInWithCallback:
can fail for many reasons, for example if there was a failure to refresh the token. In most of these cases, we would still like to get the cached token, even if it expired or about to expire. However currently there is no way to get the token if an error occurred duringrestorePreviousSignInWithCallback:
.One solution could be to make restorePreviousSignInNoRefresh public in some form.
The text was updated successfully, but these errors were encountered: