Kysely deleteMany always returns 1
authClient.signIn.email onSuccess behaviour

authClient.magicLink.verify always returns success
authClient.magicLink.verify always returns onSuccess even if the token is invalid....Admins can no longer request getFullOrganization without being member of the organization
Auth0 Pre configured oauth provider doesnt support providerId
genericOAuth plugin using the provider auth0.
Im not sure why but the auth0 provider doesnt allow for providerId to be anything but auth0 yet you could have multiple domains you wish to use that all use auth0 under the hood. Is there any history as to why multiple auth0 providers may not be possible or reasonable?...Anonymous plugin + Convex instantly clears session
[1.4.4] deleteUser Callback URL - 500 Internal Server Error
sendDeleteAccountVerification returns a 500 server error. For example the link https://example.com/api/auth/delete-user/callback?token=fdz09xm7p64xgb71t3galcifl0dgn8lh&callbackURL=/goodbye does not redirect the user back to the /goodbye page that I've created in my app.
Note: The account does get successfully deleted after following the link but results in a 500 internal server error.
Here is my auth config:...username field isn't required by default (schemas, client method)
Better-Auth sign-in broken when experimental.joins = true
experimental.joins: true is enabled in the Better-Auth config, the login always fails with "Invalid email or password", even though the entered credentials are correct.
Root cause
The client (or the auth handler) is incorrectly calling the password hash function instead of the password verify function:
auth.api.signInEmail → uses emailAndPassword.password.hash...Orphan orgs
Using incorrect date data type in mysql
timestamp. According to MySQL (https://dev.mysql.com/doc/refman/9.4/en/datetime.html#:~:text=MySQL%20retrieves%20and%20displays%20DATETIME,%3A14%3A07'%20UTC.), this type cannot store dates past 2038-01-19. Any attempt to insert a date in the future this will result in an error or a zero-date, effectively breaking the app logic.
Alter existing tables to change date columns from timestamp to datetime will fix this issue
I have a created a PR to fix this issue: https://github.com/better-auth/better-auth/pull/6366...[1.4.3] SCIM - Content-Type "application/scim+json" is not allowed
[1.4.3] Stateless Session Management – Error 'ACCOUNT_NOT_FOUND'
Stripe subscriptions issue
authClient.deleteAccount(); and creating account with the same email (google auth), my previously active subscriptions are not returned with:
```ts
const subscriptions = await auth.api.listActiveSubscriptions({
headers: await headers(),
});...Sign Out Button Keeps Loading, No Action Taken

Email verification link and password reset link not being expired after new link
additionalFields not returned in signIn
v1.4.1 - drizzle adapter doesn't support drizzle-orm@beta (rqb v2)
where: (t, { eq } => eq(t.id, 1)) syntax, whereas the rqb beta uses where: { id: 1 } syntax.
in the beta versions of drizzle, the "old" query syntax still exists on _query, which would allow drizzle beta versions to work with joins: https://rqbv2.drizzle-orm-fe.pages.dev/docs/relations-v1-v2#partial-upgrade-or-how-to-stay-on-rqb-v1-even-after-an-upgrade
...v1.4 + Postgres: id: "user_id" mapping ignored in Email OTP
emailOTP plugin ignores the global user.fields.id mapping (e.g., id: "user_id") when using the Postgres adapter in v1.4.1 (and 1.4.0-beta.20). It attempts to query the id column directly, causing a crash if the database uses a custom primary key name.
Unlike other plugins (e.g., twoFactor), the emailOTP plugin does not expose a schema configuration option, so it is impossible to manually correct the mapping as a workaround (as suggested in issue 4066 ).
1.1 What I've Tried:...[1.4.1] ctx.internalAdapter.updatePassword doesn't work since i upgrade to last version