Bug ? Wrong error message

Hi developers,

Trying to log into CommCare without any network connection and a wrong
password, the displayed error message is “Couldn’t Reach Server. Please check
your network connection”.

If I connect and can reach the server, the error message becomes the expected
one “Invalid Username or Password”.

CommCare ODK v2.17.0 (341436)

Thanks,

··· -- Charles Flèche mHealth Advisor Télécoms Sans Frontières http://www.tsfi.org Première Urgence - Aide Médicale Internationale http://www.pu-ami.org

Charles,

When you received the “Couldn’t reach server” error message, had that user
already been restored to that device (IE you had successfully logged in
with that user on that device before)? If so, this is a bug; if not, this
is expected behavior. When restoring a new user the mobile needs to pull
the OTA restore payload from the server and so requires a connection.

-Will

··· On Thu, Dec 18, 2014 at 7:31 AM, Charles Flèche wrote: > > Hi developers, > > Trying to log into CommCare without any network connection and a wrong > password, the displayed error message is "Couldn't Reach Server. Please > check > your network connection". > > If I connect and can reach the server, the error message becomes the > expected > one "Invalid Username or Password". > > CommCare ODK v2.17.0 (341436) > > Thanks, > > -- > Charles Flèche > mHealth Advisor > Télécoms Sans Frontières http://www.tsfi.org > Première Urgence - Aide Médicale Internationale http://www.pu-ami.org > > -- > > --- > You received this message because you are subscribed to the Google Groups > "CommCare Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to commcare-developers+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. >

Sorry, I should mentioned it earlier : yes the user has been logged in before.

··· On Thursday 18 December 2014 09:38:46 William Pride wrote: > with that user on that device before)? If so, this is a bug; if not, this


Charles Flèche
mHealth Advisor
Télécoms Sans Frontières http://www.tsfi.org
Première Urgence - Aide Médicale Internationale http://www.pu-ami.org

Charles

Actually, now that I think about it again I believe that’s expected
behavior as well. When the password hash doesn’t match the stored one,
CommCare attempts to contact to the server to see if the password has been
changed. When it can’t do so it gives the cannot reach server message.
Probably we should update this error message to explain that the password
might be incorrect. I’ll make a ticket to cover this, thanks for the
observation.

In the future, please report issues like this (concerning standard CommCare
usage) through the normal support channel
https://confluence.dimagi.com/display/grameenpublic/Reporting+Bugs?src=search
so
that we can address and track the issue through our normal processes.

Thanks,
Will

··· On Thu, Dec 18, 2014 at 9:43 AM, Charles Flèche wrote: > > On Thursday 18 December 2014 09:38:46 William Pride wrote: > > with that user on that device before)? If so, this is a bug; if not, this > > > Sorry, I should mentioned it earlier : yes the user has been logged in > before. > > > -- > Charles Flèche > mHealth Advisor > Télécoms Sans Frontières http://www.tsfi.org > Première Urgence - Aide Médicale Internationale http://www.pu-ami.org > > -- > > --- > You received this message because you are subscribed to the Google Groups > "CommCare Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to commcare-developers+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. >

might be incorrect. I’ll make a ticket to cover this

Cool, thanks Will.

In the future, please report issues like this (concerning standard CommCare

Woops sorry, wasn’t aware of this page.

··· On Thursday 18 December 2014 10:12:28 William Pride wrote:


Charles Flèche
mHealth Advisor
Télécoms Sans Frontières http://www.tsfi.org
Première Urgence - Aide Médicale Internationale http://www.pu-ami.org

Charles,

Sorry about the confusion here. There’s definitely a usability bug (that’s
a terrible user message), but there’s a reason the process works this way.

Basically: The phone doesn’t know if you’ve changed the password on the
server until it checks. So if you’ve logged in as “user” pw:123 before, and
your supervisor tells you that your password was too weak and it has been
changed to “Otr2p3oier3kfDa><2” and you enter that password, the phone
needs to check with the server to see whether “user”/"Otr2p3oier3kfDa><2"
is a valid user in the domain.

Thanks for reporting the issue, though, we’ll be sure to elaborate in the
UI about the distinction between an invalid password on an existing user
and a username that isn’t on the device at all.

-Clayton

··· On Thu, Dec 18, 2014 at 10:14 AM, Charles Flèche wrote: > > On Thursday 18 December 2014 10:12:28 William Pride wrote: > > might be incorrect. I'll make a ticket to cover this > > Cool, thanks Will. > > > > > In the future, please report issues like this (concerning standard > CommCare > > > Woops sorry, wasn't aware of this page. > > -- > Charles Flèche > mHealth Advisor > Télécoms Sans Frontières http://www.tsfi.org > Première Urgence - Aide Médicale Internationale http://www.pu-ami.org > > -- > > --- > You received this message because you are subscribed to the Google Groups > "CommCare Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to commcare-developers+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. >