auth-helpers: createMiddlewareSupabaseClient does not return the Session in Next.js middleware.

I’m looking into using jose as a dependency instead of js-base64. My initial tests shows there are no warnings when trying to run the build, but I need to do more test to make sure that the correct values are being returned from the token and to also make sure that the issue from #487 doesn’t return with this change. I will keep everyone updated on this thread if all tests go well and when a new release goes out. I’m still waiting to hear from the Vercel team but this will be a more immediate fix I think.

I’m closing this one out as I’ve published a new version that uses jose and it also seems that Vercel has fixed Buffer in NextJS now.

@nico-bachner the dependency we are using has Buffer in it, but if the server you are using doesn’t support Buffer it falls back to its own implementation. I reached out to the Vercel team about this and they mentioned to me that Vercel Edge Runtime now supports Buffer and the latest NextJS works fine with buffer. However upon my test with a new NextJS project while doing the build step I get warnings about Buffer being used in the dependency we are using, these warnings are to do with not even the use of Buffer but to check if Buffer is available in the first place. I created a test repo showing the warnings and asked the Vercel team to look into it but I haven’t heard back from them as yet.

https://vercel.com/changelog/improved-node-js-compatibility-for-edge-middleware-and-edge-functions

I also have this issue when the cookie token is malformed/invalid format.

@supabase/auth-helpers-nextjs: 0.7.4
@supabase/supabase-js: 2.32.0
next: 13.4.17

@j1-dev @aleix10kst @Reikon95 If you’re having the issue that was fixed it means Vercel/NextJS has changed something again. The issue isn’t with the auth-helpers but with NextJS. You should open an issue on their repository.

Same here. Suddenly my Next.js app at Vercel started falling on auth.

It seems like the issue is here: 1ea258e#diff-ab917dde7a6f132319af890fd890465d092c2787251a43b45088392a313b9608

You seem to be on the money with this one. The library relies on Buffer:

return Buffer.from(bin, 'binary').toString('base64');

Buffer is not explicitly imported in the library’s source, which may have caused the confusion.

https://nodejs.dev/en/api/v19/buffer/

I’m experiencing this as well. Worked fine up until 0.5.8

Worked when I updated next.js and auth-helpers-nextjs

@silentworks confirming the error went away for me with Next 13.3 and auth-helpers-nextjs at 0.5.9

Until someone provides a reproducible codebase with this, there isn’t much we can do. I only get a warning when using the latest version of auth-helpers, it doesn’t stop the function from working.

Also adding comments with +1 aren’t very helpful or useful.

+1 Confirmed that it breaks at 0.5.9. Using 0.5.8 as @mryechkin suggested until it is fixed.

0.5.8 doesn’t work with next 13.3

+1 help out the NextJS gang

+1 Confirmed that it breaks at 0.5.9. Using 0.5.8 as @mryechkin suggested until it is fixed.