Can I track on Client that session just started or ended?

[yuzhakovvv]

Is there an event or callback on Client that helps to track that session just started or ended?

I didn't find anything related in the docs. In my case I need to do certain actions on Client after signIn() and signOut(). This is possible with redirect: false option for credentials and email providers. But for providers like google or facebook it becomes complicated.

[balazsorban44]

Have you seen the events callbacks?

https://next-auth.js.org/configuration/events

[balazsorban44]

I am still not sure what kind of logic you are trying to run, but maybe localStorage or sessionStorage could help?

[yuzhakovvv]

In our case after Sign In we do:

1. Track of analytics "Signed In" client event
2. Redirect to a route that can happen only after Sign In and getting user data. Can't use callbackUrl here
3. Manually create a cookie

@balazsorban44 so as I understand there is no way to track on the Client that user just Signed In in the current version of next-auth?

[balazsorban44]

I think you are trying to tie the signIn client-side function call with the useSession() hook across page refreshes. React state is blown away on page refresh and so in your comment #1634 (reply in thread) in Example 1, I think 1. and 5. are indistinguishable without some extra information saved on the user's machine first (like localStorage, sessionStorage, or a client-side cookie I guess(?)).

If I understand your requirements, I don't think currently we have anything built-in for this, but you could probably solve it with some kind of a persistent client-side mechanism.

1. User opens an app for the first time. session is undefined and loading
2. session becomes null which means that user isn't signed in. Save this information into some persistent client cache
3. User signs in with signIn() and google provider
4. User is redirected to Google Auth page and enters his credentials
5. User is redirected back to an app. session is undefined and loading
6. session becomes an object
7. If client cache signals it's the first sign-in, run my logic and remove the information from the cache
8. Page refresh wouldn't run 7., as the cache doesn't signal first sign-in anymore

Maybe @iaincollins have a better idea.

[yuzhakovvv]

This is exactly what I'm doing now. Using a ?signin=true query param as persistent client state as others (localStorage, sessionStorage, or a client-side cookie) may be affected by user's browser settings.

I was wondering if there is a simpler solution out of the box 🤓

[balazsorban44]

I don't THINK there is currently, but I may be wrong. We are open for suggestions though, and if you have a good idea please open a PR! 😊