[GH-ISSUE #4795] auth.api.signUpEmail error after migration from supabase #10072

New Issue

2026-04-13T05:59:06-05:00

GiteaMirror commented

2026-04-13 05:59:06 -05:00

Originally created by @Stealthwriter on GitHub (Sep 21, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/4795

Is this suited for github?

Yes, this is suited for github

To Reproduce

I ran npx @better-auth/cli migrate

The tables where created in the public folder in supabase

but when i try to signup a user I get this error:

2025-09-21T06:55:10.847Z ERROR [Better Auth]: Failed to create user error: column "role" of relation "user" does not exist
at async signUpAction (src\app\auth\sign-up\signup-actions.tsx:45:5)
at async signUpAction (src\app\auth\sign-up\signup-actions.tsx:45:5)
43 |
44 | try {

45 | await auth.api.signUpEmail({
| ^
46 | body: {
47 | name,
48 | email, {
length: 121,
severity: 'ERROR',
code: '42703',
detail: undefined,
hint: undefined,
position: '81',
internalPosition: undefined,
internalQuery: undefined,
where: undefined,
schema: undefined,
table: undefined,
column: undefined,
dataType: undefined,
constraint: undefined,
file: 'parse_target.c',
line: '1065',
routine: 'checkInsertTargets'
}

Current vs. Expected behavior

should signup a user

What version of Better Auth are you using?

1.3

System info

nextjs

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

Backend

Auth config (if applicable)

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

Additional context

No response

Originally created by @Stealthwriter on GitHub (Sep 21, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/4795 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce I ran npx @better-auth/cli migrate The tables where created in the public folder in supabase but when i try to signup a user I get this error: 2025-09-21T06:55:10.847Z ERROR [Better Auth]: Failed to create user error: column "role" of relation "user" does not exist at async signUpAction (src\app\auth\sign-up\signup-actions.tsx:45:5) at async signUpAction (src\app\auth\sign-up\signup-actions.tsx:45:5) 43 | 44 | try { > 45 | await auth.api.signUpEmail({ | ^ 46 | body: { 47 | name, 48 | email, { length: 121, severity: 'ERROR', code: '42703', detail: undefined, hint: undefined, position: '81', internalPosition: undefined, internalQuery: undefined, where: undefined, schema: undefined, table: undefined, column: undefined, dataType: undefined, constraint: undefined, file: 'parse_target.c', line: '1065', routine: 'checkInsertTargets' } ### Current vs. Expected behavior should signup a user ### What version of Better Auth are you using? 1.3 ### System info ```bash nextjs ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript import { betterAuth } from "better-auth" export const auth = betterAuth({ emailAndPassword: { enabled: true }, }); ``` ### Additional context _No response_

GiteaMirror added the locked bug labels 2026-04-13 05:59:06 -05:00

GiteaMirror closed this issue

2026-04-13 05:59:06 -05:00

GiteaMirror commented

2026-04-13 05:59:07 -05:00

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

The error occurs because the Better Auth migration scripts do not create a role column in the user table by default for Supabase/Postgres or other supported databases. The standard schema includes fields like id, name, email, emailVerified, image, createdAt, and updatedAt, but not role source.

Your application logic or signup API is likely referencing a role column that doesn't exist in the migrated schema. To fix this, you can either:

Add a role column to your user table in Supabase (for example: ALTER TABLE "user" ADD COLUMN "role" TEXT;), or
Adjust your application logic to avoid referencing role if it isn't required.

This pattern of schema mismatches causing signup errors is established in other cases as well, such as with the name field source. If you need to add the role column, a simple TEXT type is usually sufficient unless your app requires something more specific.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Sep 21, 2025):  The error occurs because the Better Auth migration scripts do not create a `role` column in the `user` table by default for Supabase/Postgres or other supported databases. The standard schema includes fields like `id`, `name`, `email`, `emailVerified`, `image`, `createdAt`, and `updatedAt`, but not `role` [source](https://github.com/better-auth/better-auth/pull/4375). Your application logic or signup API is likely referencing a `role` column that doesn't exist in the migrated schema. To fix this, you can either: - Add a `role` column to your `user` table in Supabase (for example: `ALTER TABLE "user" ADD COLUMN "role" TEXT;`), or - Adjust your application logic to avoid referencing `role` if it isn't required. This pattern of schema mismatches causing signup errors is established in other cases as well, such as with the `name` field [source](https://github.com/better-auth/better-auth/issues/3394). If you need to add the `role` column, a simple `TEXT` type is usually sufficient unless your app requires something more specific.  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/cb89ca7a-d4e7-420c-9f4f-cfed9b7012ae?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/cb89ca7a-d4e7-420c-9f4f-cfed9b7012ae?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/cb89ca7a-d4e7-420c-9f4f-cfed9b7012ae?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/cb89ca7a-d4e7-420c-9f4f-cfed9b7012ae?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/cb89ca7a-d4e7-420c-9f4f-cfed9b7012ae?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/cb89ca7a-d4e7-420c-9f4f-cfed9b7012ae?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/cb89ca7a-d4e7-420c-9f4f-cfed9b7012ae?feedback_type=other)  [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![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/4795)

GiteaMirror commented

2026-04-13 05:59:08 -05:00

@Stealthwriter commented on GitHub (Sep 21, 2025):

but why await auth.api.signUpEmail is adding to a row column? is the issue from supabase?

await auth.api.signUpEmail({
body: {
name,
email,
password,
callbackURL: "/auth/sign-up/verified",
},

@Stealthwriter commented on GitHub (Sep 21, 2025): but why await auth.api.signUpEmail is adding to a row column? is the issue from supabase? await auth.api.signUpEmail({ body: { name, email, password, callbackURL: "/auth/sign-up/verified", },

GiteaMirror commented

2026-04-13 05:59:08 -05:00

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

Better Auth's signUpEmail only inserts fields defined in its internal user schema—like name, email, and password—and does not reference a role column by default. If you're seeing an error about the missing role column, it's likely because your application code, a plugin, or some custom logic is trying to insert or reference role during sign-up, but the migration did not create that column in Supabase. This is not an issue with Supabase itself, but rather a schema mismatch between your code and the database.

To fix this, either add a role column to your user table in Supabase, or update your code to avoid referencing role unless you actually need it. Custom fields like role require explicit schema and migration support—Better Auth won't insert extra fields unless you configure it to do so source.

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Sep 21, 2025):  Better Auth's `signUpEmail` only inserts fields defined in its internal user schema—like `name`, `email`, and `password`—and does not reference a `role` column by default. If you're seeing an error about the missing `role` column, it's likely because your application code, a plugin, or some custom logic is trying to insert or reference `role` during sign-up, but the migration did not create that column in Supabase. This is not an issue with Supabase itself, but rather a schema mismatch between your code and the database. To fix this, either add a `role` column to your `user` table in Supabase, or update your code to avoid referencing `role` unless you actually need it. Custom fields like `role` require explicit schema and migration support—Better Auth won't insert extra fields unless you configure it to do so [source](https://github.com/better-auth/better-auth/issues/3394).  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/757c7fc9-1f5d-4a53-98ac-bf7ff260b274?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/757c7fc9-1f5d-4a53-98ac-bf7ff260b274?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/757c7fc9-1f5d-4a53-98ac-bf7ff260b274?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/757c7fc9-1f5d-4a53-98ac-bf7ff260b274?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/757c7fc9-1f5d-4a53-98ac-bf7ff260b274?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/757c7fc9-1f5d-4a53-98ac-bf7ff260b274?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/757c7fc9-1f5d-4a53-98ac-bf7ff260b274?feedback_type=other)  [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![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/4795)

GiteaMirror commented

2026-04-13 05:59:09 -05:00

@Stealthwriter commented on GitHub (Sep 21, 2025):

I tried to use a basic auth.ts file and it worked fine

but when i use this auth.ts file the issue happens:

import { betterAuth } from "better-auth"
import { Pool } from "pg"
import { admin } from "better-auth/plugins"
import { anonymous } from "better-auth/plugins"
import { nextCookies } from "better-auth/next-js";
import { sendEmail } from "../utils/mailer";

export const auth = betterAuth({
emailAndPassword: {
enabled: true,
autoSignIn: false,
requireEmailVerification: true,
minPasswordLength: 8,
maxPasswordLength: 100,
sendResetPassword: async ({user, url}, request) => {
await sendEmail({
to: user.email,
subject: "Reset your password",
text: Click the link to reset your password: ${url},
html: Click the link to reset your password:<a href="${url}">${url}</a>
});
}
},
emailVerification: {
sendOnSignUp: true,
sendVerificationEmail: async ({ user, url }, request) => {
await sendEmail({
to: user.email,
subject: "Verify your email address",
text: Click the link to verify your email: ${url},
html: Click the link to verify your email:<a href="${url}">${url}</a>
});
}
},
database: new Pool({
connectionString: "postgres://postgres:hidden@db.hidden.supabase.co:5432/postgres"
}),

socialProviders: {
    google: { 
        clientId: "hidden", 
        clientSecret: "hidden", 
    }, 
},

plugins: [admin(), anonymous(), nextCookies()]

})

@Stealthwriter commented on GitHub (Sep 21, 2025): I tried to use a basic auth.ts file and it worked fine but when i use this auth.ts file the issue happens: import { betterAuth } from "better-auth" import { Pool } from "pg" import { admin } from "better-auth/plugins" import { anonymous } from "better-auth/plugins" import { nextCookies } from "better-auth/next-js"; import { sendEmail } from "../utils/mailer"; export const auth = betterAuth({ emailAndPassword: { enabled: true, autoSignIn: false, requireEmailVerification: true, minPasswordLength: 8, maxPasswordLength: 100, sendResetPassword: async ({user, url}, request) => { await sendEmail({ to: user.email, subject: "Reset your password", text: `Click the link to reset your password: ${url}`, html: `Click the link to reset your password:<a href="${url}">${url}</a>` }); } }, emailVerification: { sendOnSignUp: true, sendVerificationEmail: async ({ user, url }, request) => { await sendEmail({ to: user.email, subject: "Verify your email address", text: `Click the link to verify your email: ${url}`, html: `Click the link to verify your email:<a href="${url}">${url}</a>` }); } }, database: new Pool({ connectionString: "postgres://postgres:hidden@db.hidden.supabase.co:5432/postgres" }), socialProviders: { google: { clientId: "hidden", clientSecret: "hidden", }, }, plugins: [admin(), anonymous(), nextCookies()] })

GiteaMirror commented

2026-04-13 05:59:09 -05:00

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

The error only happens with your complex auth.ts because the admin plugin expects a role column in your user table. The default Better Auth migration does not create this column, but the admin plugin references it for role-based access control, which triggers the error during signup when the column is missing (source, source).

To fix this, add a role column to your user table in Supabase/Postgres. A simple migration would be:

ALTER TABLE "user" ADD COLUMN "role" TEXT DEFAULT 'user';

If you want stricter role management, you can use an enum type and set a default value, for example:

CREATE TYPE role_enum AS ENUM ('admin', 'user', 'retailer', 'partner');
ALTER TABLE "user" ADD COLUMN "role" role_enum NOT NULL DEFAULT 'user';

After this, your signup should work as expected with the admin plugin enabled. If you add other plugins that expect extra fields, make sure your schema matches their requirements to avoid similar issues (source).

To reply, just mention @dosu.

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

@dosubot[bot] commented on GitHub (Sep 21, 2025):  The error only happens with your complex auth.ts because the admin plugin expects a role column in your user table. The default Better Auth migration does not create this column, but the admin plugin references it for role-based access control, which triggers the error during signup when the column is missing ([source](https://github.com/better-auth/better-auth/issues/3513), [source](https://github.com/better-auth/better-auth/issues/244)). To fix this, add a role column to your user table in Supabase/Postgres. A simple migration would be: ```sql ALTER TABLE "user" ADD COLUMN "role" TEXT DEFAULT 'user'; ``` If you want stricter role management, you can use an enum type and set a default value, for example: ```sql CREATE TYPE role_enum AS ENUM ('admin', 'user', 'retailer', 'partner'); ALTER TABLE "user" ADD COLUMN "role" role_enum NOT NULL DEFAULT 'user'; ``` After this, your signup should work as expected with the admin plugin enabled. If you add other plugins that expect extra fields, make sure your schema matches their requirements to avoid similar issues ([source](https://github.com/better-auth/better-auth/issues/2405)).  *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- How did I do? [Good](https://app.dosu.dev/response-feedback/73d348ed-fa66-4e0b-b0a0-45641112553f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/73d348ed-fa66-4e0b-b0a0-45641112553f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/73d348ed-fa66-4e0b-b0a0-45641112553f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/73d348ed-fa66-4e0b-b0a0-45641112553f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/73d348ed-fa66-4e0b-b0a0-45641112553f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/73d348ed-fa66-4e0b-b0a0-45641112553f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/73d348ed-fa66-4e0b-b0a0-45641112553f?feedback_type=other)  [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/cdda13d9-dd27-4d31-b09a-5d8bec92de21/ask?utm_source=github) [![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot) [![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/4795)

Sign in to join this conversation.

Branches Tags

dependabot/npm_and_yarn/demo/electron/demo-minor-patch-36d9f2b09f

changeset-release/main

2026-07-25/fix/lefthook-postinstall

main

fix/typecheck-coverage-next

changeset-release/next

dependabot/github_actions/github-actions-16786b339b

fix/oauth-provider-session-deletion

feat/scim-demo-workflow

feat/scim-active-user-link

feat/sso-provider-user-resolution

feat/identity-provider-accounts

dependabot/npm_and_yarn/undici-7.28.0

2026-07-18/fix/expo-secure-store-async

feat/oauth-provider-remove-silence-warnings

dependabot/npm_and_yarn/vite-7.3.5

changeset-release/release/vercel-announcement

release/vercel-announcement

2026-06-29/docs/optimize-og-images

feat/yandex-social-provider

feat/ssrf-fetch-boundary

codex/pr-10225-next-comments

fix/phone-number-disable-input

perf/router-build-once

fix/oauth-user-provisioning-fields

codex/ignore-compose-override-spellcheck

2026-06-19/fix/stripe-org-reference-scope

feat/webhooks

feat/baseurl-canonical-serving-split

feat/magic-link-expires-in

fix/esbuild-security-bump

chore/sync-main-to-next-20260615

chore/revert-10053

codex/fix-expo-sdk56-dynamic-import

refactor/oauth-provider-client-authentication-module

fix/oauth-no-store-headers

claude/slack-update-stripe-docs-consistency-8Sc0w

local/fix-invite-accept-idempotency

docs/beta-mdx-component-fallback

fix/dependabot-hono-shell-quote

codex/stateless-account-cookie-resolution

fix/admin-create-user-role-escalation

feat/oauth-provider-oidc-acr

refactor/sign-in-challenges

refactor/optional-kysely-dependency

2026-06-06/chore/kysely-changeset

copilot/fix-code-review-comment

starsling/prisma-migration-reset

2026-06-02/fix/next-cookies-defer-rsc

feat/oauth-contribution-protocol

ping-maxwell/c-ping-maxwell/fix-kysely-adapter-core-utils-string-resolution-68c5

temp/server-only-test

2026-05-31/refactor/kysely-joins-json-helpers

2026-04-29/feat/google-include-granted-scopes

2026-04-29/fix/oauth-account-scope-semantics

fix/oauth-callback-path-declarative

2026-05-31/fix/sqlite-dialect-affected-rows

fix/next-cookie-separator

2026-05-29/fix/last-login-method-cookie-prefix

feat/oauth-provider-custom-subject

ping-maxwell/c-ping-maxwell/fix-error-link-apostrophe-f89a

client-assertions-main

2026-05-15/ci/fix-sqlite-abi-mismatch

2026-05-15/fix/organization-team-add-cascade

2026-05-15/fix/parse-set-cookie-value-validation

2026-05-13/feat/captcha-wildcard-endpoints

fix/i18n-before-hook-translation

fix/disable-migration-generate

2026-05-10/fix/cookie-drain-order

2026-05-10/feat/hooks-finally

2026-05-09/fix/cookie-drain-order

2026-05-09/feat/hooks-finally

2026-05-08/feat/register-before-send

fix/stripe/subscription-data-merge

2026-05-01/chore/pnpm-v11-harden

chore/pnpm-v11

2026-04-27/fix/nextcookies-idempotent-writes

2026-04-26/fix/harden-proxy-host-validation

2026-04-26/refactor/stripe-callback-signature-cleanup

2026-04-26/fix/stripe-subscription-callback-timing

2026-04-11/fix/sveltekit-app-modules

feat/open-api-zod-contract

feat/oauth-idp-initiated-bounce

2026-04-21/fix/oauth-rfc-input-validation

fix/two-factor-identity-guard

fix/resource

feat/emailpassword-authorize

feat/oauth-provider-at-hash-v2

fix/release-grep-fallback

claude/address-review-comments-JhFLr

feat/async-auth

fix/two-factor-totp-verified-enrollment

feat/plugin-ui

codex/blog-1-6-release-post

2026-04-06/fix/type-any-guards

2026-04-05/chore/downgrade-better-call

2026-04-04/ci/skip-vercel-fork-prs

2026-03-28/ci/add-autofix-ci

chore/release-preview-script

himself65/2026/02/19/role

2026-03-20/docs/improve-website

2026-03-20/fix/anonymous-onlinkaccount-expo

2026-02-17/fix/anonymous-link-state

fix/8607-saml-inresponseto

fix/8549-scim-patch-noop

v1.4.x

refactor/migration-snapshot-tests

worktree-magic-link-additional-data

chore/migrate-build-to-rollup

worktree-fix-dynamic-baseurl-8447

2026-03-06/chore/public-api-check

fix/close-8156-regression-test

fix/secondary-storage-json-error-handling

himself65/verification-namespace

cursor/issue-8307-validation-79a3

himself65/2026/01/30/error-mdx

v1.4.x-staging

fix/email-otp-user

fix/restrict-full-organization-access-roles

himself65/2026/02/12/count

himself65/2026/02/04/define-plugin

2026-02-04/feat/add-pluralize

cursor/better-auth-js-integration-ec21

cursor/expo-state-mismatch-394c

2026-02-01/fix/org-update-role-sync-members

cursor/issue-7607-investigation-e146

cursor/email-generation-helper-0ff6

himself65/2026/01/21/avoid-spread-operator

himself65/2026/01/14/cli

claude/slack-add-docs-pr-NMvgO

claude/slack-add-advanced-useplural-WHKYL

feat/hooks-pos

feat/2fa-phone

feat/2fa

fix/rotation

fix/username-check

v1.3.x

refactor/organization

feat/multiple-client-ids-social-providers

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/better-auth#10072