Ability to resend verification email #1492

Closed
opened 2018-05-18 19:14:49 +02:00 by tzarebczan · 4 comments
tzarebczan commented 2018-05-18 19:14:49 +02:00 (Migrated from github.com)

The Issue

Possibly related to https://github.com/lbryio/lbry-app/issues/997.

If a user begins the email verification process but never completes (doesn't go into email, get verification code), there is currently no way to re-send the email besides following the manual instructions to clear their login token. If they still have the old email, they can grab the verification code, but that will trigger a new email since it's expired, so they have to do it again.

Instead, we should add a link to resend verification email on the verification input screen.

System Configuration

  • LBRY Daemon version:
  • LBRY App version:
  • LBRY Installation ID:
  • Operating system:

Anything Else

Screenshots

<!-- Thanks for reporting an issue to LBRY and helping us improve! To make it possible for us to help you, please fill out below information carefully. Before reporting any issues, please make sure that you're using the latest version. - App releases: https://github.com/lbryio/lbry-app/releases - Standalone daemon: https://github.com/lbryio/lbry/releases We are also available on live chat at https://chat.lbry.io --> ## The Issue Possibly related to https://github.com/lbryio/lbry-app/issues/997. If a user begins the email verification process but never completes (doesn't go into email, get verification code), there is currently no way to re-send the email besides following the manual instructions to clear their login token. If they still have the old email, they can grab the verification code, but that will trigger a new email since it's expired, so they have to do it again. Instead, we should add a link to resend verification email on the verification input screen. ## System Configuration <!-- For the app, this info is in the About section at the bottom of the Help page. You can include a screenshot instead of typing it out --> <!-- For the daemon, run: curl 'http://localhost:5279' --data '{"method":"version"}' and include the full output --> - LBRY Daemon version: - LBRY App version: - LBRY Installation ID: - Operating system: ## Anything Else <!-- Include anything else that does not fit into the above sections --> ## Screenshots <!-- If a screenshot would help explain the bug, please include one or two here -->
amitnndn commented 2018-06-06 06:35:53 +02:00 (Migrated from github.com)

I am trying to take a dig at this one. @tzarebczan

I understand that when a user first registers their email, there is a call to LBRY API's user_email/new end point and since that one is for a new user, I am thinking that it should ideally create a conflict if I am trying to reuse the same funciton from the first step where the user enters their email for the first time.

Is there any documentation available on what kind of API calls that I can use to resend the user email. I am thinking maybe changing the end-point will work, but I am not sure what the end point is. It would be great if you could point me to any documentation that is available or provide me with the actual end point.

Thanks!

I am trying to take a dig at this one. @tzarebczan I understand that when a user first registers their email, there is a call to [LBRY API](https://api.lbry.io/user_email/new)'s ```user_email/new``` end point and since that one is for a new user, I am thinking that it should ideally create a conflict if I am trying to reuse the same funciton from the first step where the user enters their email for the first time. Is there any documentation available on what kind of API calls that I can use to resend the user email. I am thinking maybe changing the end-point will work, but I am not sure what the end point is. It would be great if you could point me to any documentation that is available or provide me with the actual end point. Thanks!
kauffj commented 2018-06-06 16:38:58 +02:00 (Migrated from github.com)

Hi @amitnndn! Thanks for taking this on.

You can call /user_email/resend_token?email=xxx@example.com.

This API is not publicly documented as it is primarily intended for our internal use.

Hi @amitnndn! Thanks for taking this on. You can call `/user_email/resend_token?email=xxx@example.com`. This API is not publicly documented as it is primarily intended for our internal use.
amitnndn commented 2018-06-06 18:09:23 +02:00 (Migrated from github.com)

Perfect! Thank you @kauffj !

Perfect! Thank you @kauffj !
tiger5226 commented 2018-06-11 04:31:30 +02:00 (Migrated from github.com)

solved and merged

solved and merged
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-desktop#1492
No description provided.