Warning: Multiple GoTrueClient instances detected

[rphlmr]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

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.

Should we worry to see this warning in browser console? (SSR, Remix Run)
It comes from: https://github.com/supabase/gotrue-js/blob/44af61e872fafbbe4a0438f8ad170f0ce5a1acdd/src/GoTrueClient.ts#L164

I have persistSession: false in createClient auth's options.

To Reproduce

Expected behavior

Screenshots

System information

• OS:[macOS
• Browser (if applies) [chrome]
• Version of supabase-js: [2.26.0]
• Version of Node.js: [18.13.0]

Additional context

[rphlmr]

Sorry for the inconvenience, I solved it by rewriting some parts of my code by creating a single instance of SupabaseClient.
Previously I used a function to create this client 'on demand',

[maaajo]

@rphlmr I'm having currently the same issue. What was the fix that solved it for you?

[rphlmr]

@rphlmr I'm having currently the same issue. What was the fix that solved it for you?

It depends what framework you use, but in Remix I do that: https://github.com/rphlmr/supa-fly-stack/blob/3b4bf3e83e79a39bf1af23b222b2adc964a850fd/app/integrations/supabase/client.ts

Basically: exporting an already instantiated supabase client (since node only load imports once).

[hf]

This issue was the exact reason we added the warning. Thanks @rphlmr!

[maaajo]

@rphlmr Thanks! I was able to find the culprit in my case. It's the Strict Mode running component twice thus causing supabase client to be created twice. When I disable strict mode the warning is gone and there is only one instance. I'm using Next JS 13 with Pages router

@hf Any ide why could this be happening? I mean this is how I set state with client (just like in the docs):

const [supabaseClient] = useState(() => createBrowserSupabaseClient())

Per my knowledge even in the strict mode this should happen only once?

[jstdk]

@hf, my app is connected to two Supabase instances, which I create separately. In this scenario, how can I prevent this warning?

[sh41]

@hf, my app is connected to two Supabase instances, which I create separately. In this scenario, how can I prevent this warning?

I had a similar issue, which I've resolved in #1100. The PR allows me to specify a different storage key for each client, which doesn't result in a warning. If multiple clients with the same storage key are instantiated the warning will still be seen.