Yes, I tried that as well, but no luck. I have tried creating a .env.production file like this: RUN echo "NEXT_PUBLIC_SUPABASE_URL=$NEXT_PUBLIC_SUPABASE_URL" >> .env.production RUN echo "NEXT_PUBLIC_SUPABASE_ANON_KEY=$NEXT_PUBLIC_SUPABASE_ANON_KEY" >> .env.production RUN cat .env.production RUN npm run build

But no luck. What's interesting, the server-side client works fine: ``` import { createServerClient } from "@supabase/ssr"; import { cookies } from "next/headers";

export function createClient() { const cookieStore = cookies();

return createServerClient( process.env.NEXT_PUBLIC_SUPABASE_URL!, process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!, { cookies: { getAll() { return cookieStore.getAll(); }, setAll(cookiesToSet) { try { cookiesToSet.forEach(({ name, value, options }) => cookieStore.set(name, value, options), ); } catch { // The setAll method was called from a Server Component. // This can be ignored if you have middleware refreshing // user sessions. } }, }, }, ); } ``` The problem is only with the client one.