User is null in nextjs api route handler

[muezz]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

I have set up auth with google in my project and it is working fine. I have set up the middleware and all the createClient functions for server and client. I have the correct auth state in both the server and the client.

But in API route handlers, I get user as null even though I am logged in.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Start a new Nextjs project.
2. Follow the docs to implement auth with the ssr package.
3. Sign in
4. Call an API endpoint where you call getSession()

Expected behavior

I should get the session info of the current user.

System information

• OS: macOS
• Browser: Arc
• Version of supabase-js: 2.43.5
• Version of supabase/ssr: 0.3.0
• Version of Node.js: 20.12.2

Additional context

I think the problem is happening because cookies are not being passed to the route handler. But I think they should be passed automatically through the middleware. Why is that not happening?

[j4w8n]

Have you checked out this article?

https://jonmeyers.io/blog/forwarding-cookies-from-server-components-to-route-handlers-with-next-js-app-router

[muezz]

@j4w8n Hmmm. It does make sense logically but there should be an easier way to do this instead of manually adding the cookies on each call. Can the middleware not do this?

[j4w8n]

@j4w8n Hmmm. It does make sense logically but there should be an easier way to do this instead of manually adding the cookies on each call. Can the middleware not do this?

I'm not familiar with Next, I just recall someone having a similar issue in the Discord community.

[muezz]

@j4w8n I will keep this open in the hope that there is an easier solution since the blog post is almost a year old.

[azharhussain96]

Can confirm that adding cookie property manually to the fetch in the server component does fix the issue. Unsure if there is something about my Next/Supabase version that is interfering with the Supabase-provided middleware boilerplate as it doesn't seem to be a ubiquitous problem.

  const response = await fetch(`${baseUrl}/api/organization`, {
    method: 'PUT',
    headers: {
      'Content-Type': 'application/json',
      'cookie': headers().get('cookie') || ''
    },
    body: JSON.stringify(orgData),
  });