then, I call this function await supabase.auth.updateUser({ password: updatePasswordForm.password })
The password gets successfully changed, however, the code after this doesn't proceed past the supabase.auth.updateUser function. There are no errors in the console or network tab...
EDIT: I'm getting this warning. Could it be because of that? Multiple GoTrueClient instances detected in the same browser context. It is not an error, but this should be avoided as it may produce undefined behavior when used concurrently under the same storage key. I know this warning gets fixed with 1.0.0, however, there is a major bug in 1.0.0 which is why I haven't updated yet.
Not sure if this is a bug.
I have password reset form.
await supabase.auth.updateUser({ password: updatePasswordForm.password })
The password gets successfully changed, however, the code after this doesn't proceed past the supabase.auth.updateUser function. There are no errors in the console or network tab...
Why is that?
"@nuxtjs/supabase": "0.3.8", "node_modules/@nuxtjs/supabase": { "version": "0.3.8", "resolved": "https://registry.npmjs.org/@nuxtjs/supabase/-/supabase-0.3.8.tgz", "integrity": "sha512-MEhfgllJx7DQX4XrycGbnTmiW6JI1wLTaVTkDV9X90q+jfBz59d/uM2E6aj4XhLuJp4GN/THGpMg8k1RfuYxqQ==", "dependencies": { "@nuxt/kit": "^3.6.1", "@supabase/supabase-js": "2.26.0", "defu": "^6.1.2", "pathe": "^1.1.1" } },
EDIT: I'm getting this warning. Could it be because of that?
Multiple GoTrueClient instances detected in the same browser context. It is not an error, but this should be avoided as it may produce undefined behavior when used concurrently under the same storage key.
I know this warning gets fixed with 1.0.0, however, there is a major bug in 1.0.0 which is why I haven't updated yet.