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 trying to use the Android Client SDK to sign in to a ZelloWork network, we're not always getting proper feedback about the error condition.
If the network name we give is just the name (i.e. "network_name" instead of "https://network_name.zellowork.com") then we seem to be getting the last error as the last time we tried to sign in.
So for example if we tried to sign in with incorrect credentials with an internet connection we do the INVALID_CREDENTIALS error as expected.
If we disable wifi and cell data and try again to sign in, the result will depend if we use network_name or if we use https://network_name.zellowork.com.
The error we get when we use network_name will be INVALID_CREDENTIALS again, even if we send a different username and/or password as last time.
But when we use https://network_name.zellowork.com we do get the NO_INTERNET_CONNECTION error as expected.
Furthermore, if we switch to a different https://another_network_name.zellowork.com we get a different behavior than if we had stayed with https://network_name.zellowork.com. With network_name the SDK keeps trying to sign in with a timer, yet with another_network_name it simply tries once and reports NO_INTERNET_CONNECTION.
The text was updated successfully, but these errors were encountered:
When trying to use the Android Client SDK to sign in to a ZelloWork network, we're not always getting proper feedback about the error condition.
If the network name we give is just the name (i.e. "network_name" instead of "https://network_name.zellowork.com") then we seem to be getting the last error as the last time we tried to sign in.
So for example if we tried to sign in with incorrect credentials with an internet connection we do the
INVALID_CREDENTIALS
error as expected.If we disable wifi and cell data and try again to sign in, the result will depend if we use
network_name
or if we usehttps://network_name.zellowork.com
.The error we get when we use
network_name
will beINVALID_CREDENTIALS
again, even if we send a different username and/or password as last time.But when we use
https://network_name.zellowork.com
we do get theNO_INTERNET_CONNECTION
error as expected.Furthermore, if we switch to a different
https://another_network_name.zellowork.com
we get a different behavior than if we had stayed withhttps://network_name.zellowork.com
. Withnetwork_name
the SDK keeps trying to sign in with a timer, yet withanother_network_name
it simply tries once and reportsNO_INTERNET_CONNECTION
.The text was updated successfully, but these errors were encountered: