loging the stack; "payload" argument must be of type object.

I am unable to register new users with my better auth/prisma NextJS app. When a user submits valid credentials, I get this error:

2025-02-20T20:33:11.442Z ERROR [Better Auth]: TypeError [TypeError: The "payload" argument must be of type object. Received null] {
  code: 'ERR_INVALID_ARG_TYPE'
}

2025-02-20T20:33:11.442Z ERROR [Better Auth]: TypeError [TypeError: The "payload" argument must be of type object. Received null] {
  code: 'ERR_INVALID_ARG_TYPE'
}

2025-02-20T20:33:11.442Z ERROR [Better Auth]: TypeError [TypeError: The "payload" argument must be of type object. Received null] {
  code: 'ERR_INVALID_ARG_TYPE'
}

2025-02-20T20:33:11.442Z ERROR [Better Auth]: TypeError [TypeError: The "payload" argument must be of type object. Received null] {
  code: 'ERR_INVALID_ARG_TYPE'
}

Ideally we would have access to log the error

.stack

.stack

.stack

.stack, is there a way to do this ?

Cchris I am unable to register new users with my better auth/prisma NextJS app. When a...

bekacru•2/20/25, 9:17 PM

this usually happens when your schema doesn't match with what better auth expects. If you haven't, use the cli to generate the schema and cross check your field with the docs.

chrisOP•2/20/25, 9:40 PM

right, that is what i have been doing. it just bit me more than a few times, and a better error would be nice (for example so i know what schema is not correct) @bekacru

chrisOP•2/20/25, 9:41 PM

but i understand how that might not be possible, some sort of onError function for the server side

Cchris right, that is what i have been doing. it just bit me more than a few times, and...

bekacru•2/20/25, 9:41 PM

The error is thrown from prisma. It's more of their issue

chrisOP•2/20/25, 9:43 PM

just thinking out loud here.. When I work with prisma directly, I can get better errors by logging the error stack

chrisOP•2/20/25, 9:45 PM

try {
  await prisma.member.delete({ where: { id: 1 } });
} catch (error) {
  console.log(error) // Useless message
  console.error(error.stack); // Helpful details
}

try {
  await prisma.member.delete({ where: { id: 1 } });
} catch (error) {
  console.log(error) // Useless message
  console.error(error.stack); // Helpful details
}

chrisOP•2/20/25, 9:45 PM

This pattern is basically required to debug Prism apps. How can I configure better auth to log the error stack in these cases so I can see the necessary information
@bekacru

Cchris This pattern is basically required to debug Prism apps. How can I configure bett...

bekacru•2/20/25, 9:47 PM

maybe by changing the logger? you can pass logger in your auth config

chrisOP•2/20/25, 9:49 PM

options..

chrisOP•2/20/25, 9:51 PM

found this https://github.com/better-auth/better-auth/blob/main/packages/better-auth/src/types/options.ts#L13](https://github.com/better-auth/better-auth/blob/848b47f56770194363476d0b8dc1ad60362a6785/packages/better-auth/src/types/options.ts#L611)

chrisOP•2/20/25, 9:52 PM

i'll dive deeper..

lonelyplanet•2/20/25, 10:53 PM

@chris add DEBUG="prisma*" to your env

lonelyplanet•2/20/25, 10:54 PM

i had almost the same error, first log message told me i had a env issue with my db connection string

loging the stack; "payload" argument must be of type object.

Similar Threads

Similar Threads

Similar Threads