Chromium loading screen issue with middleware - Safari/Firefox good - Help

Hey Vercel community! 👋

I’m running into a browser-specific authentication issue that’s got me stumped. Hoping someone has encountered this before.

The Problem:

Using Next.js 14 App Router with Supabase auth + /ssr
Google OAuth works perfectly in Safari and Firefox
Chrome and Edge get stuck on a loading screen during the auth callback
No console errors, just infinite loading after successful OAuth redirect

What I’ve tried:

Fixed cookie handling in middleware (removed multiple NextResponse.next() calls)
Added proper SameSite=lax and secure flags
Excluded auth/callback from middleware matcher
Verified redirect URLs in Supabase dashboard
```
1Current setup : 
```

1import { createServerClient } from "@supabase/ssr"2import { NextResponse, type NextRequest } from "next/server"3

export async function middleware(request: NextRequest) { // Create response once and reuse it const response = NextResponse.next({ request: { headers: request.headers, },

1})23const supabase = createServerClient(4  process.env.NEXT_PUBLIC_SUPABASE_URL!,5  process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!,6  {7    cookies: {8      get(name: string) {9        return request.cookies.get(name)?.value10      },11      set(name: string, value: string, options: any) {12        // Set cookie with Chromium-friendly options13        const cookieOptions = {14          ...options,15          httpOnly: false, // Allow client-side access for auth16          secure: process.env.NODE_ENV === 'production',17          sameSite: 'lax' as const, // More permissive for OAuth18        }19        20        response.cookies.set({21          name,22          value,23          ...cookieOptions,24        })25      },26      remove(name: string, options: any) {27        const cookieOptions = {28          ...options,29          httpOnly: false,30          secure: process.env.NODE_ENV === 'production',31          sameSite: 'lax' as const,32        }33        34        response.cookies.set({35          name,36          value: "",37          ...cookieOptions,38        })39      },40    },41  }42)4344try {45  const {46    data: { session },47    error,48  } = await supabase.auth.getSession()4950  // Set cache headers to prevent caching of auth state51  response.headers.set("Cache-Control", "no-cache, no-store, must-revalidate, private")52  response.headers.set("Pragma", "no-cache")53  response.headers.set("Expires", "0")54  response.headers.set("Vary", "Cookie")55  56  // Add CORS headers for Chromium compatibility57  response.headers.set("Access-Control-Allow-Credentials", "true")5859  if (session?.user) {60    response.headers.set("X-User-ID", session.user.id)61    response.headers.set("X-Session-Refreshed", new Date().toISOString())62  }6364  if (error) {65    console.log("[MIDDLEWARE] Auth error:", error.message)66  }67} catch (error) {68  console.error("[MIDDLEWARE] Unexpected error:", error)69}7071return response

}

export const config = { matcher: [ /* * Match all request paths except for the ones starting with: * - _next/static (static files) * - _next/image (image optimization files) * - favicon.ico (favicon file) * - public folder files * - auth/callback (OAuth callback route - IMPORTANT!) / "/((?!_next/static|_next/image|favicon.ico|auth/callback|.\.(?:svg|png|jpg|jpeg|gif|webp)$).*)", ], }

12**Questions:**341. Has anyone seen Chromium-specific issues with Supabase auth on Vercel?562. Are there known Edge Runtime limitations affecting auth callbacks?783. Any Vercel-specific configuration that helps with cross-browser OAuth?