The await updateSession() with @supabase/ssr blocks route navigations in Next.js

[trojanyao]

According to the official guide Setting up Server-Side Auth for Next.js, in step 4, there is an await updateSession() in middleware. Since there's a request await supabase.auth.getUser() in the updateSession, every time I navigate to a route that matches the middleware matcher, there's a long time to wait — that seriously affects the user experience.

Is there a better solution to this problem?

[alessiotortora]

On every request you update the session is also a problem. did you find a solution ? if you check the auth logs, there are a lot of request for auth/v1/request.

Should we block update session ? if the session is this valid ? and do the redirecting and checks in the next middleware ?