Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Channel subscriptions aren't working #13

Open
arguiot opened this issue Mar 25, 2023 · 5 comments
Open

Channel subscriptions aren't working #13

arguiot opened this issue Mar 25, 2023 · 5 comments
Labels
bug Something isn't working

Comments

@arguiot
Copy link

arguiot commented Mar 25, 2023

Bug report

When using .onMessage, I'm able to observe changes, but not using .on(.all).

Describe the bug

Here's an example:

client.connect()
socket = client.channel(.column("event_id", value: String(id), table: "messages", schema: "public"))
socket?.on(.all, callback: { msg in
      print(msg.event, msg.payload) // Won't print
})
socket?.onMessage { msg in
    print(msg.event, msg.payload) // Will print
    return msg
}
socket?.subscribe()
@arguiot arguiot added the bug Something isn't working label Mar 25, 2023
@joeldrotleff
Copy link

Yup I saw the same issue. Works fine for .on(.delete) or .on(.update), but .on(.all) doesn't work

@peterloveland
Copy link

peterloveland commented Jun 20, 2023

Did either of you find a fix or a way to circumvent the issue? I'm getting the same issue

@arguiot
Copy link
Author

arguiot commented Jun 20, 2023

I believe this might be related to Row Level Security

@joeldrotleff
Copy link

I haven't worked on this project in a while (was just hacking around to try supabase out), but iirc I didn't find any fix for this issue. This and other issues drove me back to firebase lol

@malachif-jpg
Copy link

has anyone figured this out?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants