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 our users try to sign in to Zello Work using incorrect credentials, sometimes in addition of the usual events and callbacks, Zello opens its Sign in screen (the one with the Username and Password fields and the "Sign In" button in the top right corner).
What seems to decide if this screen is launched or not is whether or not pptsdk is running in the background, in the account selection screen (titled Accounts). If the Accounts screen is dismissed (by pressing the Back button, or choosing Exit from its menu then when an user tries to login using our app they'll get the error messages and stay in our app.
Is this expected behavior? If so, is there a way to opt-out of it? In rare occasions I've seen that after we get the AppState changed events that report the INVALID_CREDENTIALS error, ZelloWork opens in the foreground and we then get another event with NONE as the last error.
The text was updated successfully, but these errors were encountered:
When our users try to sign in to Zello Work using incorrect credentials, sometimes in addition of the usual events and callbacks, Zello opens its Sign in screen (the one with the Username and Password fields and the "Sign In" button in the top right corner).
What seems to decide if this screen is launched or not is whether or not
pptsdk
is running in the background, in the account selection screen (titled Accounts). If the Accounts screen is dismissed (by pressing the Back button, or choosing Exit from its menu then when an user tries to login using our app they'll get the error messages and stay in our app.Is this expected behavior? If so, is there a way to opt-out of it? In rare occasions I've seen that after we get the
AppState
changed events that report theINVALID_CREDENTIALS
error, ZelloWork opens in the foreground and we then get another event withNONE
as the last error.The text was updated successfully, but these errors were encountered: