createServerClient deprecated?

[k-thornton]

Hey there! I'm noticing that this line has been marked deprecated in @supabase/ssr. It says the get/set/remove needs to be replaced with getAll/setAll and that the current method won't be supported in the next release. I haven't dug in much further but wanted to raise the issue here as soon as I noticed it.

https://github.com/vercel/nextjs-subscription-payments/blob/25a19504c85a2353f23e907521d0cdb1979c66d6/utils/supabase/server.ts#L10C10-L10C28

[k-thornton]

Ported the latest code over from the Supabase docs and opened a PR :)

[SgtErnestBilko]

I have updated my middleware (updateSession) as suggested. I am getting intermittent 502 errors, which I can resolve by deleting cookies for the site and re-logging on. When in the 502 'dead-end', if I comment out

cookiesToSet.forEach(({ name, value, options }) =>
            supabaseResponse.cookies.set(name, value, options),
          );

The 502 error disappears and the page renders. I have spent hours trying to catch errors in ever more granular ways but I'm none the wiser. Every solution involves preventing a set cookies call in some way.

I am going to open a discussion in supabase '502 Errors with updated createServerClient code', so as not to hijack this thread.

[SgtErnestBilko]

Discussion here. https://github.com/orgs/supabase/discussions/30185