Hi everyone, I am currently encountering issues with

subscriptions

. I'm using

NextJS

and I use a hook in 2 different pages to setup the subscription that is basically this (copied from the

nextjs-slack-clone

official example):

...
  useEffect(() => {
    const messageListener = sb
      .from<Message>("message")
      .on("INSERT", (payload) => setTempNewMessage(payload.new))
      .subscribe((event, e) => {
        console.warn(`[Message] Listener ${event}`, messageListener);
        if (e) {
          console.error("[Message] Listener error", e);
        }
      });

    console.error("STARTED LISTENING...", messageListener);
    // Cleanup on unmount
    return () => {
      messageListener
        .unsubscribe()
        .receive("ok", () => console.error("!SUBSCRIPTION REMOVED!"));
    };
  }, []);

At the first page load, the subscription is all good and works perfectly. But when I do

router.push

to the other page, it unsubscribe correctly but the new subscription starts

CLOSED

and even the

RETRYING_AFTER_TIMEOUT

does nothing. Any ideas?

Hello @NARCISO! This thread has been automatically created from your message in #843999948717555735 a ``few seconds ago``. Pinging @User so that they see this as well! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ... menu) and select Leave Thread to unsubscribe from future updates. Want to change the title? Use the

/title

command! We have solved your problem? Click the button below to archive it.

I don't use Next.js but if both useEffects are called, the subscription would be combined to 1 as only one connection is allowed. Then when you leave page if you close subscription it closes both. BUT I don't know if both get called before you do the router.push or 1 is called and then the 2nd is called only after router.push.

Subscription not starting after page routing

I have this logs

I agree it looks in parallel, but man .008 seconds from telling server leave to join... not sure what that would do.

I'll try with a delay of 1 sec and let's see

I meant series not parallel

Yeah yeah

I think that is a bug then, you might report in github realtime

I will

So if you don't kill the subscription, and call it again it just gets replaced

I tried removing the

unsubscribe

but it does not replace it. Actually,

NextJS

seems to close the subscription automatically.

Yeah, sorry as I said I don't use nextJS... supabase.js/realtime.js though is supposed to only allow 1 subscription to same "event" type on a table/filter.

Maybe it's something @supabase/supabase-auth-helpers is doing

But I guess if you have multiple handlers on it they would both tirgger

well then I don't know ahah

But at least report your traces in realtime and they can figure out where the issue is. You have some nice traces that help.

Yeah I will include the screenshots I sent in this chat

Thread was archived by @NARCISO. Anyone can send a message to unarchive it.