Postgres Changes channel / real-time not working

[RyanTippsTX]

Bug report

Describe the bug

Using the new supabase-js 2.0.0-rc.3, and following the guide exactly, the channel is left undefined AND no payload is ever delivered when the I insert/update a row in the DB.

I have tried:

• created a new Supabase DB today, with one public table, enabled Realtime on the table, did not enable RLS
• verified my pub anon key & url is correct
• verified I have 2.0.0-rc.3 in my package.json
• tried with Firefox & Chrome
• tried with NextJS/React & now Vite/React

I also tried making an equivalent repo but with supabase-js v1 and the equivalent subscription method, and I do get a "subscription" object returned (woohoo!), but I still never get a payload when i insert/update the DB.

To Reproduce

create a fresh React repo with Vite,
edit only the App.jsx per my screenshot below.

Expected behavior

1. Subscriptions to return a subscription object (or something)
2. and for a payload to be delivered when I add/edit the DB.

Screenshots

System information

• macOS Monterey
• firefox, chrome
• node v16.15.0

[GaryAustin1]

I had v2 realtime code that worked yesterday and stopped this morning. Unfortunately have not been able to look at the details other than

.subscribe((status)=>console.log(status))

now returns "CHANNEL_ERROR".

Did not see anything at quick glance in the websocket messages, but had to leave it until tomorrow.
I assume maybe the realtime server update to the new presence version broke v2 code, but I'm really not sure with how little I got to look this morning.

[w3b6x9]

@RyanTippsTX Hey, I just replied to your tweet regarding the same but can you please take a look at #169?

[RyanTippsTX]

.subscribe((status)=>console.log(status))

^Thank you @GaryAustin1, i didn't know you could do this, this was helpful for troubleshooting. Is this documented somewhere in the docs?

@RyanTippsTX Hey, I just replied to your tweet regarding the same but can you please take a look at #169?

@w3b6x9 Yes! Disabling strict mode does subscribe me to realtime! However the first issue still remains: the subscribe method still returns undefined, so I am unable to teardown the connection with supabase.removeChannel(channel).

I just tried putting the .channel().on().subscribe() call in an async / await IIFE, and the method is definitely returning undefined (i.e. I'm not just console-logging the value before the method returns).

[RyannGalea]

I'm having some issues here too, unable to unsubscribe from the existing channel to re-sub to it as it returns nothing,

In my Angular project.

Edit: I've solved the 'undefined' issue by setting the var and then subscribing afterward. But I still seem to miss changes randomly, mostly on the first call.

      this.realtime = this.ss.client
        .channel( `public:contact:id=eq.${contact.id}`)
        .on('postgres_changes', {
            event: 'UPDATE', schema: 'public',
            table: 'contact', filter: `id=eq.${contact.id}`,
          },
          ({new: contact}) => {
            console.log('contact', contact)
            this.contact = merge(this.contact, contact)
        })

      this.realtime.subscribe()

[w3b6x9]

Is this documented somewhere in the docs?

@RyanTippsTX I'll make sure to update the docs as they're outdated at the moment.

[w3b6x9]

Alright everyone, please version bump to supabase-js v2.0.0-rc.4 where the channel will be returned after calling subscribe.

[RyanTippsTX]

Woohoo! - confirmed its working for me on rc.4 !!

[GaryAustin1]

rc.4 also fixes my issue.