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

Better Auth toISOString is not a function Error with New User Creation #1845

New Issue
Closed
opened 2026-03-13 09:07:44 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-03-13 09:07:44 -05:00
Owner
Copy Link

Originally created by @summerisgood1 on GitHub (Sep 4, 2025).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

Try to create a new user account (either via Google OAuth)
The signup process fails with the timestamp error
Existing users can still sign in normally

Current vs. Expected behavior

I'm experiencing an error with Better Auth when trying to create new users. Existing users can sign in successfully, but new user creation fails with the following error:

2025-09-04T15:36:26.328Z ERROR [Better Auth]: TypeError: value.toISOString is not a function
2025-09-04T15:36:26.329Z ERROR [Better Auth]: unable_to_create_user

Expected Behavior
New users should be able to sign up and sign in successfully, just like existing users.

Actual Behavior
New user creation fails with TypeError: value.toISOString is not a function and unable_to_create_user errors.

What version of Better Auth are you using?

^1.3.4

System info

System:
    OS: macOS 15.5
    CPU: (12) arm64 Apple M3 Pro
    Memory: 140.00 MB / 18.00 GB
    Shell: 5.9 - /bin/zsh
  Browsers:
    Chrome: 139.0.7258.155
    Edge: 139.0.3405.125
    Safari: 18.5

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

Client

Auth config (if applicable)

export const auth = betterAuth({
  database: drizzleAdapter(db, {
    provider: "pg",
    schema: {
      user: schema.users,
      account: schema.accounts,
      session: schema.sessions,
      verification: schema.verifications,
    },
  }),
  emailAndPassword: {
    enabled: true,
  },
  socialProviders: {
    google: {
      clientId: process.env.AUTH_GOOGLE_ID!,
      clientSecret: process.env.AUTH_GOOGLE_SECRET!,
    },
  },
  session: {
    fields: {
      expiresAt: "expires",
      token: "sessionToken",
    },
  },
  account: {
    fields: {
      providerId: "provider",
      accountId: "providerAccountId",
      refreshToken: "refresh_token",
      accessToken: "access_token",
      idToken: "id_token",
    },
  },
});

Additional context

This is a T3 Stack project using Next.js, TypeScript, and Drizzle ORM
The project was migrated from NextAuth.js to Better Auth
The error only affects new user creation, not existing user authentication
All database migrations have been applied successfully

Database Schema

export const users = createTable("user", (d) => ({
  id: d
    .varchar({ length: 255 })
    .notNull()
    .primaryKey()
    .$defaultFn(() => crypto.randomUUID()),
  name: d.varchar({ length: 255 }),
  email: d.varchar({ length: 255 }).notNull(),
  // newEmailVerified fill null with false
  newEmailVerified: boolean("email_verified")
    .$defaultFn(() => false)
    .notNull(),

  image: d.varchar({ length: 255 }),
  // createdAt fill null with now
  createdAt: timestamp("created_at", { withTimezone: true })
    .$defaultFn(() => /* @__PURE__ */ new Date())
    .notNull(),
  // updatedAt fill null with now
  updatedAt: timestamp("updated_at", { withTimezone: true })
    .$defaultFn(() => /* @__PURE__ */ new Date())
    .notNull(),
  // useless in better-auth
  isRulesAgreed: d.boolean().notNull().default(false),
  emailVerified: d
    .timestamp({
      mode: "date",
      withTimezone: true,
    })
    .default(sql`CURRENT_TIMESTAMP`),
}));

export const accounts = createTable(
  "account",
  (d) => ({
    // id fill null with provider + providerAccountId
    id: text("id").primaryKey(),
    userId: d
      .varchar({ length: 255 })
      .notNull()
      .references(() => users.id),
    providerAccountId: d.varchar({ length: 255 }).notNull(),
    provider: d.varchar({ length: 255 }).notNull(),
    access_token: d.text(),
    refresh_token: d.text(),
    // transform expires_at to accessTokenExpiresAt
    accessTokenExpiresAt: timestamp("access_token_expires_at", {
      withTimezone: true,
    }),
    refreshTokenExpiresAt: timestamp("refresh_token_expires_at", {
      withTimezone: true,
    }),
    scope: d.varchar({ length: 255 }),
    id_token: d.text(),
    password: text("password"),
    // createdAt fill null with now
    createdAt: timestamp("created_at", { withTimezone: true }).notNull(),
    // updatedAt fill null with now
    updatedAt: timestamp("updated_at", { withTimezone: true }).notNull(),
    // Legacy NextAuth field; kept as plain varchar for backward compatibility
    type: d.varchar({ length: 255 }).notNull(),
    expires_at: d.integer(),
    token_type: d.varchar({ length: 255 }),
    session_state: d.varchar({ length: 255 }),
  }),
  (t) => [
    //primaryKey({ columns: [t.provider, t.providerAccountId] }),
    index("account_user_id_idx").on(t.userId),
  ],
);

export const sessions = createTable(
  "session",
  (d) => ({
    // id fill null with sessionToken
    id: text("id").primaryKey(),
    userId: d
      .varchar({ length: 255 })
      .notNull()
      .references(() => users.id),
    sessionToken: d.varchar({ length: 255 }).notNull(),
    expires: d.timestamp({ mode: "date", withTimezone: true }).notNull(),
    ipAddress: text("ip_address"),
    userAgent: text("user_agent"),
    // createdAt fill null with now
    createdAt: timestamp("created_at", { withTimezone: true }).notNull(),
    // updatedAt fill null with now
    updatedAt: timestamp("updated_at", { withTimezone: true }).notNull(),
  }),
  (t) => [index("t_user_id_idx").on(t.userId)],
);



export const verifications = createTable("verification", {
  id: text("id").primaryKey(),
  identifier: text("identifier").notNull(),
  value: text("value").notNull(),
  expiresAt: timestamp("expires_at", { withTimezone: true }).notNull(),
  createdAt: timestamp("created_at", { withTimezone: true }).$defaultFn(
    () => /* @__PURE__ */ new Date(),
  ),
  updatedAt: timestamp("updated_at", { withTimezone: true }).$defaultFn(
    () => /* @__PURE__ */ new Date(),
  ),
});
Originally created by @summerisgood1 on GitHub (Sep 4, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce Try to create a new user account (either via Google OAuth) The signup process fails with the timestamp error Existing users can still sign in normally ### Current vs. Expected behavior I'm experiencing an error with Better Auth when trying to create new users. Existing users can sign in successfully, but new user creation fails with the following error: 2025-09-04T15:36:26.328Z ERROR [Better Auth]: TypeError: value.toISOString is not a function 2025-09-04T15:36:26.329Z ERROR [Better Auth]: unable_to_create_user Expected Behavior New users should be able to sign up and sign in successfully, just like existing users. Actual Behavior New user creation fails with TypeError: value.toISOString is not a function and unable_to_create_user errors. ### What version of Better Auth are you using? ^1.3.4 ### System info ```bash System: OS: macOS 15.5 CPU: (12) arm64 Apple M3 Pro Memory: 140.00 MB / 18.00 GB Shell: 5.9 - /bin/zsh Browsers: Chrome: 139.0.7258.155 Edge: 139.0.3405.125 Safari: 18.5 ``` ### Which area(s) are affected? (Select all that apply) Client ### Auth config (if applicable) ```typescript export const auth = betterAuth({ database: drizzleAdapter(db, { provider: "pg", schema: { user: schema.users, account: schema.accounts, session: schema.sessions, verification: schema.verifications, }, }), emailAndPassword: { enabled: true, }, socialProviders: { google: { clientId: process.env.AUTH_GOOGLE_ID!, clientSecret: process.env.AUTH_GOOGLE_SECRET!, }, }, session: { fields: { expiresAt: "expires", token: "sessionToken", }, }, account: { fields: { providerId: "provider", accountId: "providerAccountId", refreshToken: "refresh_token", accessToken: "access_token", idToken: "id_token", }, }, }); ``` ### Additional context This is a T3 Stack project using Next.js, TypeScript, and Drizzle ORM The project was migrated from NextAuth.js to Better Auth The error only affects new user creation, not existing user authentication All database migrations have been applied successfully Database Schema ``` export const users = createTable("user", (d) => ({ id: d .varchar({ length: 255 }) .notNull() .primaryKey() .$defaultFn(() => crypto.randomUUID()), name: d.varchar({ length: 255 }), email: d.varchar({ length: 255 }).notNull(), // newEmailVerified fill null with false newEmailVerified: boolean("email_verified") .$defaultFn(() => false) .notNull(), image: d.varchar({ length: 255 }), // createdAt fill null with now createdAt: timestamp("created_at", { withTimezone: true }) .$defaultFn(() => /* @__PURE__ */ new Date()) .notNull(), // updatedAt fill null with now updatedAt: timestamp("updated_at", { withTimezone: true }) .$defaultFn(() => /* @__PURE__ */ new Date()) .notNull(), // useless in better-auth isRulesAgreed: d.boolean().notNull().default(false), emailVerified: d .timestamp({ mode: "date", withTimezone: true, }) .default(sql`CURRENT_TIMESTAMP`), })); export const accounts = createTable( "account", (d) => ({ // id fill null with provider + providerAccountId id: text("id").primaryKey(), userId: d .varchar({ length: 255 }) .notNull() .references(() => users.id), providerAccountId: d.varchar({ length: 255 }).notNull(), provider: d.varchar({ length: 255 }).notNull(), access_token: d.text(), refresh_token: d.text(), // transform expires_at to accessTokenExpiresAt accessTokenExpiresAt: timestamp("access_token_expires_at", { withTimezone: true, }), refreshTokenExpiresAt: timestamp("refresh_token_expires_at", { withTimezone: true, }), scope: d.varchar({ length: 255 }), id_token: d.text(), password: text("password"), // createdAt fill null with now createdAt: timestamp("created_at", { withTimezone: true }).notNull(), // updatedAt fill null with now updatedAt: timestamp("updated_at", { withTimezone: true }).notNull(), // Legacy NextAuth field; kept as plain varchar for backward compatibility type: d.varchar({ length: 255 }).notNull(), expires_at: d.integer(), token_type: d.varchar({ length: 255 }), session_state: d.varchar({ length: 255 }), }), (t) => [ //primaryKey({ columns: [t.provider, t.providerAccountId] }), index("account_user_id_idx").on(t.userId), ], ); export const sessions = createTable( "session", (d) => ({ // id fill null with sessionToken id: text("id").primaryKey(), userId: d .varchar({ length: 255 }) .notNull() .references(() => users.id), sessionToken: d.varchar({ length: 255 }).notNull(), expires: d.timestamp({ mode: "date", withTimezone: true }).notNull(), ipAddress: text("ip_address"), userAgent: text("user_agent"), // createdAt fill null with now createdAt: timestamp("created_at", { withTimezone: true }).notNull(), // updatedAt fill null with now updatedAt: timestamp("updated_at", { withTimezone: true }).notNull(), }), (t) => [index("t_user_id_idx").on(t.userId)], ); export const verifications = createTable("verification", { id: text("id").primaryKey(), identifier: text("identifier").notNull(), value: text("value").notNull(), expiresAt: timestamp("expires_at", { withTimezone: true }).notNull(), createdAt: timestamp("created_at", { withTimezone: true }).$defaultFn( () => /* @__PURE__ */ new Date(), ), updatedAt: timestamp("updated_at", { withTimezone: true }).$defaultFn( () => /* @__PURE__ */ new Date(), ), }); ```
GiteaMirror added the bug label 2026-03-13 09:07:44 -05:00
GiteaMirror commented 2026-03-13 09:07:46 -05:00
Author
Owner
Copy Link

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

Hi @15077693d! I'm Dosu and I’m helping the better-auth team.

The error happens because Better Auth expects certain fields (like createdAt, updatedAt, or possibly emailVerified) to be JavaScript Date objects during new user creation, but something in your schema or migration is providing a non-Date value (like a string, boolean, or null). When Better Auth tries to call .toISOString() on this value, it throws the error you’re seeing. This only affects new users because existing users already have valid date objects stored in the database.

The root cause is likely in how Drizzle ORM and your schema interact with Better Auth’s adapter. The adapter’s transformInput function will call .toISOString() on date fields if config.supportsDates is false and the value is a Date, but if the value isn’t a Date, you get this error. This can happen if your $defaultFn or SQL default isn’t returning a Date object as expected, or if the migration left a field as null or a string instead of a Date object [source].

To fix this, make sure your Drizzle schema for all timestamp fields (createdAt, updatedAt, emailVerified, etc.) always provides a real Date object during user creation. For example, use .$defaultFn(() => new Date()) for all relevant fields, and check that your migrations don’t leave these fields as null or strings. If you’re missing an auto-update for updatedAt, you can add .$onUpdate(() => new Date()) as a workaround [source].

If you’re still seeing the error after these changes, double-check the actual values being passed to Better Auth for those fields during signup—logging them before user creation can help pinpoint which one isn’t a Date.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Sep 4, 2025): <!-- Greeting --> Hi @15077693d! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the better-auth team. <!-- Answer --> The error happens because Better Auth expects certain fields (like createdAt, updatedAt, or possibly emailVerified) to be JavaScript Date objects during new user creation, but something in your schema or migration is providing a non-Date value (like a string, boolean, or null). When Better Auth tries to call `.toISOString()` on this value, it throws the error you’re seeing. This only affects new users because existing users already have valid date objects stored in the database. The root cause is likely in how Drizzle ORM and your schema interact with Better Auth’s adapter. The adapter’s `transformInput` function will call `.toISOString()` on date fields if `config.supportsDates` is false and the value is a Date, but if the value isn’t a Date, you get this error. This can happen if your `$defaultFn` or SQL default isn’t returning a Date object as expected, or if the migration left a field as null or a string instead of a Date object [[source]](https://github.com/better-auth/better-auth/blob/c29fabe0dcba116d894b1477a4d65824c5d04a90/packages/better-auth/src/adapters/create-adapter/index.ts). To fix this, make sure your Drizzle schema for all timestamp fields (createdAt, updatedAt, emailVerified, etc.) always provides a real Date object during user creation. For example, use `.$defaultFn(() => new Date())` for all relevant fields, and check that your migrations don’t leave these fields as null or strings. If you’re missing an auto-update for `updatedAt`, you can add `.$onUpdate(() => new Date())` as a workaround [[source]](https://github.com/better-auth/better-auth/issues/4187). If you’re still seeing the error after these changes, double-check the actual values being passed to Better Auth for those fields during signup—logging them before user creation can help pinpoint which one isn’t a Date. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/d8fbe058-8c9b-4d91-8604-1a5e086a99fa?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/d8fbe058-8c9b-4d91-8604-1a5e086a99fa?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/d8fbe058-8c9b-4d91-8604-1a5e086a99fa?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/d8fbe058-8c9b-4d91-8604-1a5e086a99fa?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d8fbe058-8c9b-4d91-8604-1a5e086a99fa?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/d8fbe058-8c9b-4d91-8604-1a5e086a99fa?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/d8fbe058-8c9b-4d91-8604-1a5e086a99fa?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/4434)
GiteaMirror commented 2026-03-13 09:07:48 -05:00
Author
Owner
Copy Link

@ping-maxwell commented on GitHub (Sep 5, 2025):

What endpoint are you calling? is it just failing on social login?

@ping-maxwell commented on GitHub (Sep 5, 2025): What endpoint are you calling? is it just failing on social login?
GiteaMirror commented 2026-03-13 09:07:49 -05:00
Author
Owner
Copy Link

@summerisgood1 commented on GitHub (Sep 5, 2025):

What endpoint are you calling? is it just failing on social login?

GET /api/auth/get-session 200 in 1598ms
 POST /api/auth/sign-in/social 200 in 151ms
 GET /api/auth/get-session 200 in 32ms
2025-09-05T01:12:48.868Z ERROR [Better Auth]: TypeError: value.toISOString is not a function
2025-09-05T01:12:48.868Z ERROR [Better Auth]: unable_to_create_user
 GET /api/auth/callback/google?state=haiZ-mYuvn1-qF5bHGqKNLR_7ME&code=4%2F0AVMBsJThEroaCyS2LLcajSFFDxdoK-_z3Z_Gg5M-tNtiQ&scope=email+profile+openid+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email&authuser=0&prompt=none 302 in 404ms
 GET /api/auth/error?error=unable_to_create_user 200 in 31ms

I have only social login.

@summerisgood1 commented on GitHub (Sep 5, 2025): > What endpoint are you calling? is it just failing on social login? ``` GET /api/auth/get-session 200 in 1598ms POST /api/auth/sign-in/social 200 in 151ms GET /api/auth/get-session 200 in 32ms 2025-09-05T01:12:48.868Z ERROR [Better Auth]: TypeError: value.toISOString is not a function 2025-09-05T01:12:48.868Z ERROR [Better Auth]: unable_to_create_user GET /api/auth/callback/google?state=haiZ-mYuvn1-qF5bHGqKNLR_7ME&code=4%2F0AVMBsJThEroaCyS2LLcajSFFDxdoK-_z3Z_Gg5M-tNtiQ&scope=email+profile+openid+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email&authuser=0&prompt=none 302 in 404ms GET /api/auth/error?error=unable_to_create_user 200 in 31ms ``` I have only social login.
GiteaMirror commented 2026-03-13 09:07:49 -05:00
Author
Owner
Copy Link

@summerisgood1 commented on GitHub (Sep 5, 2025):

@dosu Can you update my database schema to solve the problem?

@summerisgood1 commented on GitHub (Sep 5, 2025): @dosu Can you update my database schema to solve the problem?
GiteaMirror commented 2026-03-13 09:07:50 -05:00
Author
Owner
Copy Link

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

To fix the error, update your schema so all timestamp fields (like createdAt, updatedAt, and emailVerified) are always JavaScript Date objects—not strings, booleans, or null. For Drizzle ORM, use .$defaultFn(() => new Date()) or .defaultNow() for these fields, and avoid { mode: "string" } for timestamps. For updatedAt, add .$onUpdate(() => new Date()) if you want it to auto-update. Also, make sure emailVerified is a timestamp (Date or null), not a boolean—this is a common migration mistake that causes this exact error [source].

Here’s how your users table should look:

export const users = createTable("user", (d) => ({
  id: d.varchar({ length: 255 }).notNull().primaryKey().$defaultFn(() => crypto.randomUUID()),
  name: d.varchar({ length: 255 }),
  email: d.varchar({ length: 255 }).notNull(),
  image: d.varchar({ length: 255 }),
  createdAt: d.timestamp("created_at", { withTimezone: true }).$defaultFn(() => new Date()).notNull(),
  updatedAt: d.timestamp("updated_at", { withTimezone: true }).$defaultFn(() => new Date()).$onUpdate(() => new Date()).notNull(),
  emailVerified: d.timestamp("email_verified", { withTimezone: true }).default(null), // must be Date or null
  isRulesAgreed: d.boolean().notNull().default(false),
}));

Apply similar changes to your accounts, sessions, and verifications tables: use .$defaultFn(() => new Date()) or .defaultNow() for all timestamp fields, and ensure they are typed as Date. This will prevent the 'toISOString is not a function' error during new user creation [source].

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Sep 5, 2025): <!-- Answer --> To fix the error, update your schema so all timestamp fields (like createdAt, updatedAt, and emailVerified) are always JavaScript Date objects—not strings, booleans, or null. For Drizzle ORM, use .$defaultFn(() => new Date()) or .defaultNow() for these fields, and avoid { mode: "string" } for timestamps. For updatedAt, add .$onUpdate(() => new Date()) if you want it to auto-update. Also, make sure emailVerified is a timestamp (Date or null), not a boolean—this is a common migration mistake that causes this exact error [[source]](https://github.com/better-auth/better-auth/blob/e812142c6cb91a65bba022b77f1176f7cca6dff2/packages/better-auth/src/adapters/create-adapter/index.ts). Here’s how your users table should look: ```typescript export const users = createTable("user", (d) => ({ id: d.varchar({ length: 255 }).notNull().primaryKey().$defaultFn(() => crypto.randomUUID()), name: d.varchar({ length: 255 }), email: d.varchar({ length: 255 }).notNull(), image: d.varchar({ length: 255 }), createdAt: d.timestamp("created_at", { withTimezone: true }).$defaultFn(() => new Date()).notNull(), updatedAt: d.timestamp("updated_at", { withTimezone: true }).$defaultFn(() => new Date()).$onUpdate(() => new Date()).notNull(), emailVerified: d.timestamp("email_verified", { withTimezone: true }).default(null), // must be Date or null isRulesAgreed: d.boolean().notNull().default(false), })); ``` Apply similar changes to your accounts, sessions, and verifications tables: use .$defaultFn(() => new Date()) or .defaultNow() for all timestamp fields, and ensure they are typed as Date. This will prevent the 'toISOString is not a function' error during new user creation [[source]](https://github.com/better-auth/better-auth/issues/1418). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/52a3f8fb-3663-4122-b047-eb3db582d9fa?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/52a3f8fb-3663-4122-b047-eb3db582d9fa?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/52a3f8fb-3663-4122-b047-eb3db582d9fa?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/52a3f8fb-3663-4122-b047-eb3db582d9fa?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/52a3f8fb-3663-4122-b047-eb3db582d9fa?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/52a3f8fb-3663-4122-b047-eb3db582d9fa?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/52a3f8fb-3663-4122-b047-eb3db582d9fa?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/better-auth/better-auth/issues/4434)
GiteaMirror commented 2026-03-13 09:07:50 -05:00
Author
Owner
Copy Link

@summerisgood1 commented on GitHub (Sep 5, 2025):

What endpoint are you calling? is it just failing on social login?

May I have your help please?

@summerisgood1 commented on GitHub (Sep 5, 2025): > What endpoint are you calling? is it just failing on social login? May I have your help please?
GiteaMirror commented 2026-03-13 09:07:51 -05:00
Author
Owner
Copy Link

@summerisgood1 commented on GitHub (Sep 5, 2025):

Damnnnn... I throught drizzleAdapter mapping need actual key in db instead of object key.
There have no error after add user:{emailVerified: newEmailVerified}

@summerisgood1 commented on GitHub (Sep 5, 2025): Damnnnn... I throught drizzleAdapter mapping need actual key in db instead of object key. There have no error after add user:{emailVerified: newEmailVerified}
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
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#1845
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?