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

Missing details/tryAgain property from RATE_LIMITED error from verifyApiKey #1344

New Issue
Closed
opened 2026-03-13 08:34:05 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-03-13 08:34:05 -05:00
Owner
Copy Link

Originally created by @opswiz on GitHub (Jun 11, 2025).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

  • Update from v1.2.8 to v1.2.9
  • The RATE_LIMITED error from auth.api.verifyApiKey used to have details object with tryAgainIn value
  • After update its missing

Current vs. Expected behavior

After upgrading from v1.2.8 -> v1.2.9. The details.tryAgainIn property is missing from RATE_LIMITED error returned by the verifyApiKey method.

Image

Is this intentional? I used this to forward the value to the client if there is a rate limit error and was quite helpful

What version of Better Auth are you using?

1.2.9

Provide environment information

- MacOs
- Nextjs 15

Which area(s) are affected? (Select all that apply)

Package

Auth config (if applicable)

import { betterAuth } from "better-auth"
export const auth = betterAuth({
  emailAndPassword: {  
    enabled: true
  },
});

Additional context

No response

Originally created by @opswiz on GitHub (Jun 11, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce - Update from v1.2.8 to v1.2.9 - The `RATE_LIMITED` error from `auth.api.verifyApiKey` used to have details object with tryAgainIn value - After update its missing ### Current vs. Expected behavior After upgrading from v1.2.8 -> v1.2.9. The `details.tryAgainIn` property is missing from `RATE_LIMITED` error returned by the `verifyApiKey` method. <img width="944" alt="Image" src="https://github.com/user-attachments/assets/df86b180-b9d8-435a-9c53-df1f04e9999f" /> Is this intentional? I used this to forward the value to the client if there is a rate limit error and was quite helpful ### What version of Better Auth are you using? 1.2.9 ### Provide environment information ```bash - MacOs - Nextjs 15 ``` ### Which area(s) are affected? (Select all that apply) Package ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ emailAndPassword: { enabled: true }, }); ``` ### Additional context _No response_
GiteaMirror added the nextjsbug labels 2026-03-13 08:34:05 -05:00
GiteaMirror commented 2026-03-13 08:34:06 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Sep 10, 2025):

Hi, @opswiz. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that after upgrading from v1.2.8 to v1.2.9, the RATE_LIMITED error from auth.api.verifyApiKey no longer includes the details.tryAgainIn property.
  • This missing property affects your retry timing logic.
  • You asked if the removal of this property was intentional.
  • There have been no comments or responses on this issue so far.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of better-auth by commenting here.
  • If I don’t hear back within 7 days, I will automatically close this issue.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 10, 2025): Hi, @opswiz. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that after upgrading from v1.2.8 to v1.2.9, the `RATE_LIMITED` error from `auth.api.verifyApiKey` no longer includes the `details.tryAgainIn` property. - This missing property affects your retry timing logic. - You asked if the removal of this property was intentional. - There have been no comments or responses on this issue so far. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of better-auth by commenting here. - If I don’t hear back within 7 days, I will automatically close this issue. Thanks for your understanding and contribution!
GiteaMirror commented 2026-03-13 08:34:07 -05:00
Author
Owner
Copy Link

@opswiz commented on GitHub (Sep 10, 2025):

Yes this issue still exists and relevant. @dosubot

@opswiz commented on GitHub (Sep 10, 2025): Yes this issue still exists and relevant. @dosubot
GiteaMirror commented 2026-03-13 08:34:08 -05:00
Author
Owner
Copy Link

@ping-maxwell commented on GitHub (Oct 2, 2025):

We don't support inferring errors yet, which is why types are not appearing. But the value should be there, you can just type-cast it until we support it.

@ping-maxwell commented on GitHub (Oct 2, 2025): We don't support inferring errors yet, which is why types are not appearing. But the value should be there, you can just type-cast it until we support it.
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 bug nextjs
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#1344
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?