github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 22:32:01 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #541] Resend OTP code doesn't work #8313

New Issue
Closed
opened 2026-04-13 03:23:01 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-13 03:23:01 -05:00
Owner
Copy Link

Originally created by @ywyher on GitHub (Nov 15, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/541

when a user register i send an email containing the OTP required to verify his email using :

  await emailOtp.verifyEmail({
      email: email,
      otp: otp
  })

it does work successfully as expected, the issue is if the user doesn't receive the email
for this case i added a button that send the OTP again using

  await emailOtp.sendVerificationOtp({
      email: email,
      type: "email-verification",
  }

the function does add a record on the verification table without deleting the previous OTP code record, but when the user receive his new OTP code and try to verify the email with it, it throws invalid OTP, when i try the old OTP code it works
btw if i manually remove the previous OTP code record from the database, the new code works normally
is there a way to solve this ?

i was gonna try to delete the previous OTP code record from the database programmatically but there is no field in the verification table that i can use to indicate which OTP code belongs to which user

  • OS: arch linux
  • Browser: firefox
  • Version: better-auth "0.8.3"
Originally created by @ywyher on GitHub (Nov 15, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/541 when a user register i send an email containing the OTP required to verify his email using : ```tsx await emailOtp.verifyEmail({ email: email, otp: otp }) ``` it does work successfully as expected, the issue is if the user doesn't receive the email for this case i added a button that send the OTP again using ```tsx await emailOtp.sendVerificationOtp({ email: email, type: "email-verification", } ``` the function does add a record on the verification table **without deleting the previous OTP code record**, but when the user receive his new OTP code and try to verify the email with it, it throws invalid OTP, when i try the old OTP code it works btw if i manually remove the previous OTP code record from the database, the new code works normally is there a way to solve this ? i was gonna try to delete the previous OTP code record from the database programmatically but there is no field in the verification table that i can use to indicate which OTP code belongs to which user - OS: arch linux - Browser: firefox - Version: better-auth "0.8.3"
GiteaMirror added the locked label 2026-04-13 03:23:01 -05:00
GiteaMirror commented 2026-04-13 03:23:02 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Nov 17, 2024):

this should be fixed. Feel free to re-open if this is still an issue.

<!-- gh-comment-id:2481257414 --> @Bekacru commented on GitHub (Nov 17, 2024): this should be fixed. Feel free to re-open if this is still an issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label locked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#8313
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?