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

All subscriptions fail if publication not turned on for any table that is subscribed to. #248

Open
yowzadave opened this issue Mar 15, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@yowzadave
Copy link

Bug report

If subscribing to multiple tables, and any of the subscribed tables does not have publication turned on, the subscription to all tables will fail, with no error being thrown.

To Reproduce

If I have two tables, cats and dogs, and I have only added cats to the publication, then do something like:

const channel = supabase
  .channel("test")
  .on(
    "postgres_changes",
    { event: "update", schema: "public", table: "cats" },
    (payload) => console.log(payload)
  )
  .on(
    "postgres_changes",
    { event: "update", schema: "public", table: "dogs" },
    (payload) => console.log(payload)
  )
  .subscribe();

...then no subscription events will be fired, regardless of whether the cats or dogs table has been updated.

No error is provided to indicate that the subscription has failed.

@yowzadave yowzadave added the bug Something isn't working label Mar 15, 2023
@kangmingtay kangmingtay transferred this issue from supabase/supabase-js Aug 24, 2023
@w3b6x9
Copy link
Member

w3b6x9 commented Sep 5, 2023

@yowzadave thanks for the feedback here. will discuss this will the realtime team. cc/ @chasers

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

2 participants