The updated client-manifest.js is correctly written when adding the new route but the dev server seems to be serving the old one regardless. I also tried by switching browsers (Brave -> Chrome if relevant) after creating the route and still got the same result so some server-side caching ...
@naripok there is a workaround for v1, how you can handle this error (for v2 see next comment): async createSupabaseClient() { const supabase = createClient(SUPABASE_URL, SUPABASE_ANON_KEY, { // disable the call to getSessionFromUrl in the constructor detectSessionInUrl: false, }); /...