Ali Raza Khalid

The same issue is being discussed [here](https://github.com/nextauthjs/next-auth/issues/11074#issue-2334069653) in detail. I might also tell you that there is a way to check for some error but that also seems to broken...

we can customize the authorize() function to return custom errors like this https://github.com/nextauthjs/next-auth/pull/9871 And here https://github.com/nextauthjs/next-auth/issues/9099 But to be honest I am not sure how to implement these.

https://github.com/nextauthjs/next-auth/issues/11074#issuecomment-2184315761 Follow here for discussions.

https://github.com/nextauthjs/next-auth/issues/11074#issuecomment-2205152161 Please follow this issue for details

I see you have provided link to my repo but I don't understand your issue. For me the user.id in the session is same as that returned by the database.

I have implemented custom sessions with callbacks the following way: ```import NextAuth from "next-auth"; import GitHub from "next-auth/providers/github"; import Google from "next-auth/providers/google"; import CredentialsProvider from "next-auth/providers/credentials"; import { SignInWithEmailAndPassword, oauthSignIn,...

I only problem I have faces is with the trigger to update the session when I verify user email and I think it is some of my personal error. For...

Actually the docs are in migration currently so some features are explained in the old documentation.

`await unstable_update({ user: { ...session.user, isVerified: true } }); ` Also tried this way but does not seem to work

No I tried several ways before but was not successfull I will try again !