shadow Comments - Answer Overflow

shadow

Explore posts from servers

•Created by shadow on 4/16/2025 in #bug-reports

Email Verification required and Captcha return the same error code

Suggestion: It’d be much cleaner if the backend returned a more specific error code or identifier in the response body. For example:

  {
  "status": 403,
  "code": "EMAIL_NOT_VERIFIED",
  "message": "You need a verified email address to login."
}

  {
  "status": 403,
  "code": "EMAIL_NOT_VERIFIED",
  "message": "You need a verified email address to login."
}

And

{
  "status": 403,
  "code": "CAPTCHA_FAILED",
  "message": "Captcha verification failed."
}

{
  "status": 403,
  "code": "CAPTCHA_FAILED",
  "message": "Captcha verification failed."
}

This would allow the frontend to handle each case with proper context, like:

switch (ctx.error.code) {
  case "EMAIL_NOT_VERIFIED":
    toast.error("Please verify your email address. A verification link has been sent.");
    break;
  case "CAPTCHA_FAILED":
    toast.error("Captcha failed. Please try again.");
    break;
  default:
    toast.error("Access denied.");
}

switch (ctx.error.code) {
  case "EMAIL_NOT_VERIFIED":
    toast.error("Please verify your email address. A verification link has been sent.");
    break;
  case "CAPTCHA_FAILED":
    toast.error("Captcha failed. Please try again.");
    break;
  default:
    toast.error("Access denied.");
}

Let me know if this is already possible and I missed something — or if there’s a workaround. Thanks! 🙌

3 replies

BABetter Auth

•Created by shadow on 3/28/2025 in #help

Middleware in a Better Auth Project

yep that's what I thought, thanks for the clarification! by the way, great project!

5 replies

BABetter Auth

•Created by shadow on 3/7/2025 in #help

Trigger annualDiscountPriceId on Stripe

Something happened because now it returns the correct array with the subscription, closing issue.

5 replies

BABetter Auth

•Created by shadow on 3/7/2025 in #help

Trigger annualDiscountPriceId on Stripe

5 replies

BABetter Auth

•Created by shadow on 2/27/2025 in #help

Error generating schemas.

Here is my file structure:

.
├── app
│   ├── api
│   │   └── auth
│   │       └── [...all]
│   │           └── route.ts
│   ├── favicon.ico
│   ├── globals.css
│   ├── layout.tsx
│   └── page.tsx
├── components.json
├── eslint.config.mjs
├── lib
│   ├── auth-client.ts
│   ├── auth.ts
│   └── utils.ts
├── middleware.ts
├── next.config.ts
├── package-lock.json
├── package.json
├── postcss.config.mjs
├── public
│   ├── file.svg
│   ├── globe.svg
│   ├── next.svg
│   ├── vercel.svg
│   └── window.svg
├── tailwind.config.ts
└── tsconfig.json

.
├── app
│   ├── api
│   │   └── auth
│   │       └── [...all]
│   │           └── route.ts
│   ├── favicon.ico
│   ├── globals.css
│   ├── layout.tsx
│   └── page.tsx
├── components.json
├── eslint.config.mjs
├── lib
│   ├── auth-client.ts
│   ├── auth.ts
│   └── utils.ts
├── middleware.ts
├── next.config.ts
├── package-lock.json
├── package.json
├── postcss.config.mjs
├── public
│   ├── file.svg
│   ├── globe.svg
│   ├── next.svg
│   ├── vercel.svg
│   └── window.svg
├── tailwind.config.ts
└── tsconfig.json

(This is a fresh NextJS project where i made it until step 4 in https://www.better-auth.com/docs/installation#configure-database, including step 4)

5 replies

BABetter Auth

•Created by shadow on 1/15/2025 in #help

Added additional field, but authClient.signUp.email doesnt accept it

why i am getting this error when isFirst is true? am i correctly using the admin plugin?

{
      code: "UNAUTHORIZED",
      status: 401,
      statusText: "UNAUTHORIZED"
}

{
      code: "UNAUTHORIZED",
      status: 401,
      statusText: "UNAUTHORIZED"
}

4 replies

Gaming

Programming