Realtime connection immediately closes

Hey friends!

I'm attempting to use the "next" version of

supabase-js

supabase-js

supabase-js

supabase-js (I'm on

1.36.0-next.29

1.36.0-next.29

1.36.0-next.29

1.36.0-next.29 specifically) to get realtime updates for a specific table. I've enabled realtime on the table, ensured that all replication toggles are on for the

supabase_realtime

supabase_realtime

supabase_realtime

supabase_realtime replication, and enabled my table as a source for that replication.

Here's the relevant client code:

    supabase
      .channel('*')
      .on('postgres_changes', { event: '*', schema: 'public', table: 'posts' }, (payload: any) => {
        console.log('Change received!', payload)
      })
      .subscribe()

    supabase
      .channel('*')
      .on('postgres_changes', { event: '*', schema: 'public', table: 'posts' }, (payload: any) => {
        console.log('Change received!', payload)
      })
      .subscribe()

    supabase
      .channel('*')
      .on('postgres_changes', { event: '*', schema: 'public', table: 'posts' }, (payload: any) => {
        console.log('Change received!', payload)
      })
      .subscribe()

    supabase
      .channel('*')
      .on('postgres_changes', { event: '*', schema: 'public', table: 'posts' }, (payload: any) => {
        console.log('Change received!', payload)
      })
      .subscribe()

I'm in a React/TS app. The behavior that I'm seeing is that no updates are logged. When digging into the websocket messages, I see that the client immediately sends messages with events

phx_join, access_token, phx_leave

phx_join, access_token, phx_leave

phx_join, access_token, phx_leave

phx_join, access_token, phx_leave. All are acked, including with a

phx_close

phx_close

phx_close

phx_close message at the end. It continues to send heartbeats. Did I discover a bug in latest, or am I doing something wrong that causes the client to immediately leave?

garyaustin•8/23/22, 9:01 PM

https://github.com/supabase/realtime-js/issues/169#issuecomment-1224707844
I've not figured out the relation between -next and @supabase/supabase-js@2.0.0-rc.6 (which is the release recommended in that bug report.)

GitHub

When used with react strict mode, the realtime database does not su...

Bug report Describe the bug When we develop with the React strict mode, we can't build subscriptions correctly. To Reproduce Turn on strict mode: ReactDOM.createRoot(document.getElementById...

garyaustin•8/23/22, 9:04 PM

Also my channel name had to have the table/filter details to work. 'public.table:uid=eq.23' . But I don't remember what the failure was without that. I tested something like 'mychannel' and that did not work.

BloodyaugustOP•8/23/22, 9:09 PM

I expected to run into issues with React18 and the double

useEffect

useEffect

which I worked around with a ref counter. I've verified I'm only subscribing once.

garyaustin•8/23/22, 9:18 PM

I'm not sure about react other than watching the issues.
It is running for me with Sveltekit no problem right now (except for the delay issue they need to resolve until there is really a subscription).

BloodyaugustOP•8/23/22, 9:23 PM

The

subscribe

subscribe

callback is giving me this error: CHANNEL_ERROR Error: mismatch between server and client bindings for postgres changesCHANNEL_ERROR Error: mismatch between server and client bindings for postgres changes

garyaustin•8/23/22, 9:23 PM

Never seen that one...

garyaustin•8/23/22, 9:26 PM

Did you switch to rc.6?

BloodyaugustOP•8/23/22, 9:29 PM

@garyaustin Switching to rc.6 fixed it! Sounds like a bug in

1.36.0-next.29

1.36.0-next.29

garyaustin•8/23/22, 9:32 PM

There still is a bug overall in that it takes several seconds before you can receive update messages.

garyaustin•8/23/22, 9:33 PM

https://github.com/supabase/realtime/issues/282

GitHub

Subscription seems to take a few seconds to initialize · Issue #282...

Bug report Describe the bug I'm experimenting with building a very simple realtime chat application in Vue 3. I'm using a subscription to monitor my posts table on INSERT to keep th...

Realtime connection immediately closes

Similar Threads

Similar Threads

Similar Threads