JWT user missing values after logging in

[DennisSpek]

Question 💬

I ran into some issues regarding the JWT user being null after a succesfull login.

Did some debugging in the callbacks and saw the following:

2 {
  token: {
    token: {
      name: null,
      email: null,
      picture: null,
      sub: 'e1d4c887-0257-4543-be37-c9b297e2cce6'
    },
    user: {
      id: 'e1d4c887-0257-4543-be37-c9b297e2cce6',
      emailVerified: '2022-09-06T09:54:24.163Z',
      name: null,
      email: null,
      image: null
    },
    account: {
      providerAccountId: '[email protected]',
      type: 'email',
      provider: 'email'
    },
    isNewUser: false,
    iat: 1662458064,
    exp: 1665050064,
    jti: '521054a5-7ead-43fc-94f4-f5eb7fffde43'
  }
}

I read through the docs and noticed that the correct callback flow would be: signin -> JWT -> Session.
It is possible to return the user object found within the signIn callback, but this is not getting passed into the JWT callback.

Due to the fact that some properties like isNewUser are filled in correctly, could the missing user info be related to a DB issue?

What are some things I could further check in the hopes of solving this issue?

How to reproduce ☕️

Not available

Contributing 🙌🏽

No, I am afraid I cannot help regarding this

[DennisSpek]

Just a quickl followup on this question in the hopes someone knows the answer;

I also noticed that when I use getToken, the sub key within the object contains the same string as I have assigned to the user I am trying to log in.