AEricHarty
commented
6 years ago All good except when I had it send me 4 codes, the third had only 3 digits for some reason and wouldn't work. Must be something strange in the code gen algorithm.
Open jinitokazama opened 6 years ago
AEricHarty
commented
6 years ago All good except when I had it send me 4 codes, the third had only 3 digits for some reason and wouldn't work. Must be something strange in the code gen algorithm.
Check for Email Validation. (Perhaps a pin input or a link that redirects in the email)
Email validation acceptance criteria (flexible): -When the user registers, a code is sent and the client opens the ResultFrag -ResultFrag should have Submit, Resend and Back to Registration buttons -If the user closes the app while on this screen it should reopen to this screen next time(onStop->savedInstanceState) -If the user hits resend or goes back and registers again they should be sent a new code(will need a new Post since the Resend button in ResultFrag shouldn't keep the password)* -Server side, if registration db add fails check if verified is 0 then give them a new code, if 1 then fail them -Validation codes should time out and be purged from the db (now it's own story) -If the user inputs a code that is timed out or incorrect they should receive a warning that old codes time out, may want to hit resend -Login should check verified row, if 0 then don't log in
*Allowing re-registration will take some server side logic since the user could put in a different password and our salt would make it impossible to tell. Or if they had a typo in their email the first time, we want to replace it.