Start a new topic
Answered

Impossible verifyEmail workflow

Hi Damien



there is a problem with the verifyEmail workflow.



1) Sign up new user via Kinvey.User.signup. Don't click on the verification email yet.



2) Refresh the page, Kinvey.init now returns an error. Not an active user with getEmailVerification() == "sent", not success with no active user, but error with "name":"EmailVerificationRequired". That's weird but not impossible yet.



3) At this point new Kinvey.Metadata(Kinvey.getActiveUser()).getEmailVerification() equals to null, so you can't really tell what is the status of the email verification and



4) If you try to log in with the newly created user you get error "name":"AlreadyLoggedIn","description":"You are already logged in with another user.". But Kinvey.getActiveUser() is null. That's weird but not impossible yet.



5) Despite you are "AlreadyLoggedIn" you can not log out. Kinvey.User.logout() returns error "name":"MissingAppCredentials". So you have to ask your user to manually delete the user session.



6) After Kinvey.init finally returns success with activeUser == null you can try to log in with the newly created user only to get error "name":"EmailVerificationRequired". At this point you have exhausted all possibilities for logging in with unverified user. That means you can't get the Kinvey.getActiveUser().username which is required for resending the verification email via Kinvey.User.verifyEmail.



The verifyEmail workflow is impossible.

Best Answer

Hi Daniel,


My name is Thomas Conner and I looked into the issue you were having with verifying emails. I wanted inform you we added some more information to the dev center regarding email verification. http://devcenter.kinvey.com/html5/guides/users#signup


The second callout under Signup now recommends storing the user returned from a successful signup if you are using email verification. You can then retrieve this user sometime later to resend the verification email or check its status. 


I think this workaround will work. Thanks

Answer

Hi Daniel,


My name is Thomas Conner and I looked into the issue you were having with verifying emails. I wanted inform you we added some more information to the dev center regarding email verification. http://devcenter.kinvey.com/html5/guides/users#signup


The second callout under Signup now recommends storing the user returned from a successful signup if you are using email verification. You can then retrieve this user sometime later to resend the verification email or check its status. 

Daniel,


We are looking into this now.  Can you confirm the steps above are still accurate?


Thanks,

Hi Damien


unless you fixed anything I think it is still an issue :). We have still not released our product so there are no users and I did not check this in some time but I can have a look and let you know.


Thanks

@peterholcomb: I will escalate this ticket on our end to see if we can get it resolved in a more timely fashion. Thanks,
I'm also seeing this error. You should at least be able to log out an unverified user. Also, it would be nice to be able to get their username so you could resend the verification email.
Daniel,



This has been added to Jira and should be addressed at some point this development sprint. At this time you are the only person to report this bug, but it is possible that it is affecting other customers. We are unsure about the size / effort for a fix but we're confident you should see one in the next week or so.



Thanks,
Hi Damien



any update on this? This must be affecting all your customers.



Thanks

Hi Damien,



We're luckily at a stage where this isn't a huge issue but it is causing quite a delay in general development of the app.



-Steve
Daniel,



We haven't been able to follow up on this yet, we have a development sprint wrapping up tonight and should have a little time between sprints to verify this error.



I will keep you posted. Is this something you can work around for the time being?



Thanks,
Morning Daniel,



We are working to reproduce and verify this internally. I will follow up later today on this issue.



Thanks,
Login or Signup to post a comment