useSupabaseRedirectCookie() from nuxt/supabase module gets overwritten by chrome dev tools
Hi guys,
I am using the nuxt/supabase module and I am trying to get the redirect after login working by using the useSupabaseRedirectCookie() composable from the module.
The problem is that the cookie value is being overwritten with "/.well-known/appspecific/com.chrome.devtools.json" no matter what route I enter before. When I look up all request with that cookie in the network tab I can see that every request after the login page load is having the wrong value.
Do you have any ideas if I am missing anything or have you encountered that issue before?
2 Replies
Hi @StormiCParK. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry, but the knowledge sources provided do not contain any information about the useSupabaseRedirectCookie() composable from the nuxt/supabase module, nor do they mention issues with Chrome DevTools overwriting its value or related redirect problems.
The closest related information is about Supabase's default redirect behavior in Nuxt, which can be configured or disabled in the module options, but there is no mention of the specific cookie issue or interaction with Chrome DevTools. If you are experiencing unexpected cookie values like "/.well-known/appspecific/com.chrome.devtools.json", it may be related to your development environment or browser extensions, but this is not covered in the provided sources. For further troubleshooting, you may want to consult the official Nuxt Supabase documentation or open an issue on their GitHub repository for more targeted supportNuxt.js localhost redirects to /login automatically, resulting in 404 error Part 2.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
<@146295316335820800> Kapa.ai is still learning and improving, please let me know how I did by reacting below.