Error when updating session expiresAt
Hi, whenever better-auth decides to update my session's expiresAt field, it crashes.
Here's the error:
```
2992 }...
Limited access to webhook events
In the current structure the better-auth plugin only allows different events but not all of them for example customer.created event was excluded in the allowed events and i need it to update my database on users so can help me track user subscription state
404 with stripe plugin
hey all im getting a 404 when trying to get a stripe url:
```ts
const { data, error } = await client.subscription.upgrade({
annual: biAnnual,
plan: 'basic',...
`auth.api.forgotPassword` not throwing error
For this configuration:
```ts
export const auth = betterAuth({
database: new Pool({...
TwoFactor plugins requires id column in schema?
I'm getting the following error message, when calling ...
authClient.twoFactor.enable:
# SERVER_ERROR: [BetterAuthError: The field "id" does not exist in the "twoFactor" schema. Please update your drizzle schema or re-generate using "npx @better-auth/cli generate".] {
cause: undefined
}
# SERVER_ERROR: [BetterAuthError: The field "id" does not exist in the "twoFactor" schema. Please update your drizzle schema or re-generate using "npx @better-auth/cli generate".] {
cause: undefined
}
Solution:
will be updated
API Key Metadata is null?
For this configuration with v1.2.3:
```
export const auth = betterAuth({
database: drizzleAdapter(db, {...
Performance of `auth.api.hasPermission` seem to be very slow
Do I need to create indexes in my sqlite database to improve it? [solved]
Stripe | BetterAuth webhooks in Cloudflare need to be async error (FIXED)
Using BetterAuth on CloudFlare Pages (with Sveltekit in my case) brings this error when trying to use the Webhooks from Stripe (Based on the Docs):
The question is, if every environment supports Async or if you now need to decide if it should be async or sync based on the environment....
"WEBHOOK_ERROR_SUBTLECRYPTOPROVIDER_CANNOT_BE_USED_IN_A_SYNCHRONOUS_CONTEXTUSE_AWAIT_CONSTRUCTEVENTASYNC_INSTEAD_OF_CONSTRUCTEVENT",
"message":
"Webhook Error: SubtleCryptoProvider cannot be used in a synchronous context. Use `await constructEventAsync(...)` instead of `constructEvent(...)`",
"WEBHOOK_ERROR_SUBTLECRYPTOPROVIDER_CANNOT_BE_USED_IN_A_SYNCHRONOUS_CONTEXTUSE_AWAIT_CONSTRUCTEVENTASYNC_INSTEAD_OF_CONSTRUCTEVENT",
"message":
"Webhook Error: SubtleCryptoProvider cannot be used in a synchronous context. Use `await constructEventAsync(...)` instead of `constructEvent(...)`",
Solution:
Fixed by newest update 1.2.4
Disabling the default team requires you to provide a function for a default team
I want to disable the default team created from the org plugin entirely, but I'm required to give a function still
New update makes my plugin error
the 1.2 update made my plugin throw
on the client side, everything works as expect, but the error is there....
Type never has no call signatures.
Type never has no call signatures.
Stripe | Make success_url optional?
Hey, when using embedded as ui_mode using the basic subscription implementation you get this error: "
success_url is not supported with ui_mode: embedded."
So my question is, if we could make success_url optional (and maybe more not sure if the cancelUrl needs also to be optional), so we can use it together in a embedded mode.
Not sure if this is a feature_request or bug, but i think a nice to have for everyone not wanting to use the default stripe hosted pages....Stripe Plugin bug
authClient.subscription.upgrade() does not work with prisma, it says a column is missing even though the prisma studio shows it exists, the neon dashboard says it exists, and I can access the field using the prisma adapter in my code no problem.
``
# SERVER_ERROR: [Error [PrismaClientValidationError]:
Invalid db[getModelName(model)].create()` invocation in...Solution:
Probably because you made
stripeSubscriptionId required in your schema.
Just go to your schema.prisma and remove the ? on stripeSubscriptionId: String?
It has to be optional because this val comes from stripe, and is put in the db down the line by the webhook handler built into better-auth...Stripe Plugin | Received unknown parameters: params, options
As the Title states using for example: ``` getCheckoutSessionParams: async ({ user, session, plan, subscription }, request) => {
return {
params: {
allow_promotion_codes: true,
tax_id_collection: {...
Solution:
update to 1.2.2
Admin Plugin Issue with better-auth 1.2.1
found a type compatibility issue between the admin plugin and better-auth 1.2.1. the admin plugin's init function expects the old authcontext interface, but 1.2.1 requires a runMigrations property that's missing in the plugin. this causes typescript errors when trying to use the admin plugin with the updated library
Stripe Plugin | Bugs To Fix
"@better-auth/stripe": "^1.2.1",
"better-auth": "^1.2.1",
"@better-auth/stripe": "^1.2.1",
"better-auth": "^1.2.1",
mapProfileToUser doesn't work when using ID token authentication
Hi, great work on Better Auth!
When using ID tokens to log in into a sign in provider (e.g. Google with ID token and access token, as aspecified here ),
mapProfileToUser parameters are not passed to the user object, thus not being stored in the database neither.
I've set up additionalAttributes on the user object. If those are required, Prisma complains about those parameters not being specified while creating the user object. If those are not required they are just left as null
Backend auth.ts...Social Login state mismatch error
I migrated to v 1.2 and this broke the apple and google logins for my site. I couldn't figure out what exactly was wrong as the oauth flow wasn't completing successfully. I got this logs in my server `this is the server error logs 2025-03-03T06:39:36: ^[[2m2025-03-03T06:39:36.790Z^[[0m ^[[31mERROR^[[0m ^[[1m[Better Auth]:^[[0m State Mismatch. Verification not found { stat>
2025-03-03T06:39:36: # SERVER_ERROR: TypeError: Cannot read properties of undefined (reading 'get')
2025-03-03T06:39:36: at <unknown> (.next/server/chunks/903.js:299:18339)
2025-03-03T06:39:36: at Object.r [as handler] (.next/server/chunks/903.js:84:105326)
2025-03-03T06:39:36: at async y (.next/server/chunks/903.js:84:93446)...
Solution:
This has been solved in 1 2.3
twoFactor.verifyTotp missing trustDevice: true
I’m a little bit confused about trustDevice: true.
It works with:
twoFactor.verifyOtp
...