BA
Better Auth•2w ago
Duki

Unknown argument `stripeCustomerId` when creating customer on signup

Hey, I'm having a new issue where updating the user's stripeCustomerId automatically on signup, gives me a prisma error. I found an other thread here where the issue was the schema not having stripeCustomerId set as optional, but my schema does. Has anyone else had this issue?
Solution:
ok yea it was my fault. I got a warning from prisma to set an output path for the generated client Warning: You did not specify an output path for your generator in schema.prisma. This behavior is deprecated and will no longer be supported in Prisma 7.0.0., but then forgot to change the PrismaClient import statement from the old default path.
Jump to solution
5 Replies
Duki
DukiOP•2w ago
I'm using BA and BA stripe plugin v1.2.7 and prisma client v6.6.0
Unknown argument `stripeCustomerId`. Available options are marked with ?.
at An (/Users/duki/IdeaProjects/simple-recipe-app/node_modules/@prisma/client/runtime/library.js:29:1363)
at zn.handleRequestError (/Users/duki/IdeaProjects/simple-recipe-app/node_modules/@prisma/client/runtime/library.js:121:7102)
at zn.handleAndLogRequestError (/Users/duki/IdeaProjects/simple-recipe-app/node_modules/@prisma/client/runtime/library.js:121:6784)
at zn.request (/Users/duki/IdeaProjects/simple-recipe-app/node_modules/@prisma/client/runtime/library.js:121:6491)
at async l (/Users/duki/IdeaProjects/simple-recipe-app/node_modules/@prisma/client/runtime/library.js:130:9778)
at async Object.update (file:///Users/duki/IdeaProjects/simple-recipe-app/node_modules/better-auth/dist/adapters/prisma-adapter/index.mjs:145:16)
at async Object.update (file:///Users/duki/IdeaProjects/simple-recipe-app/node_modules/better-auth/dist/shared/better-auth.rSYJCd3o.mjs:433:19)
at async after (file:///Users/duki/IdeaProjects/simple-recipe-app/node_modules/@better-auth/stripe/dist/index.mjs:1069:38)
at async createWithHooks (file:///Users/duki/IdeaProjects/simple-recipe-app/node_modules/better-auth/dist/shared/better-auth.Bk5IMdhM.mjs:56:9)
at async Object.createUser (file:///Users/duki/IdeaProjects/simple-recipe-app/node_modules/better-auth/dist/shared/better-auth.Bk5IMdhM.mjs:156:27) {
clientVersion: '6.6.0'
}
Unknown argument `stripeCustomerId`. Available options are marked with ?.
at An (/Users/duki/IdeaProjects/simple-recipe-app/node_modules/@prisma/client/runtime/library.js:29:1363)
at zn.handleRequestError (/Users/duki/IdeaProjects/simple-recipe-app/node_modules/@prisma/client/runtime/library.js:121:7102)
at zn.handleAndLogRequestError (/Users/duki/IdeaProjects/simple-recipe-app/node_modules/@prisma/client/runtime/library.js:121:6784)
at zn.request (/Users/duki/IdeaProjects/simple-recipe-app/node_modules/@prisma/client/runtime/library.js:121:6491)
at async l (/Users/duki/IdeaProjects/simple-recipe-app/node_modules/@prisma/client/runtime/library.js:130:9778)
at async Object.update (file:///Users/duki/IdeaProjects/simple-recipe-app/node_modules/better-auth/dist/adapters/prisma-adapter/index.mjs:145:16)
at async Object.update (file:///Users/duki/IdeaProjects/simple-recipe-app/node_modules/better-auth/dist/shared/better-auth.rSYJCd3o.mjs:433:19)
at async after (file:///Users/duki/IdeaProjects/simple-recipe-app/node_modules/@better-auth/stripe/dist/index.mjs:1069:38)
at async createWithHooks (file:///Users/duki/IdeaProjects/simple-recipe-app/node_modules/better-auth/dist/shared/better-auth.Bk5IMdhM.mjs:56:9)
at async Object.createUser (file:///Users/duki/IdeaProjects/simple-recipe-app/node_modules/better-auth/dist/shared/better-auth.Bk5IMdhM.mjs:156:27) {
clientVersion: '6.6.0'
}
I already migrated the new schema as well 🤔 I even reset the db and the problem still remains Perhaps I am still not understanding prisma and how to properly migrate the schema changes to the prisma client 🙈
Ping
Ping•2w ago
Does everything else work? Maybe if so it might not be schema migration issue? Not certain though. 🤔
Duki
DukiOP•2w ago
Havent tried yet, but i think its on my end, because if i try to manually update the user, i dont even get the ahtocomplete from typescript for that field. Something must be wrong with my generator i think. Will take a look when I get to it and report back.
Ping
Ping•2w ago
🫡 Sounds good. Also just tested on my end and everything works fine. But not using Prisma, using Drizzle, so likely different story.
Solution
Duki
Duki•2w ago
ok yea it was my fault. I got a warning from prisma to set an output path for the generated client Warning: You did not specify an output path for your generator in schema.prisma. This behavior is deprecated and will no longer be supported in Prisma 7.0.0., but then forgot to change the PrismaClient import statement from the old default path.

Did you find this page helpful?