2.49.9 breaks realtime features on expo 53 in some conditions

[christophemenager]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

• Upgrading from 2.49.8 to any version above (including .next) seems to break some realtime feature in react-native

To Reproduce

It's hard to describe as not all my listeners to postgres_changes are impacted.

Here's one listener that does not work after upgrade:

  const channel = getConversationsChannel({ gameId })
    .on(
      'postgres_changes',
      {
        event: 'INSERT',
        schema: 'public',
        table: 'message',
        filter: `game_id=eq.${gameId}`,
      },
      ({ new: newMessage }) => {
        receiveRemoteMessage(newMessage as RemoteMessagePayload);
      },
    )
    .subscribe();

By "does not work" I mean:

• The insertion in the message table occurs
• The debug tool of realtime in the supabase dashboard shoes the event in the channel
• No data is received on the mobile app side

I have another realitme listener that works perfectly fine in my app, which is built the same way.

Maybe there is an issue with the number of sockets opened?

Expected behavior

The event should be logged on mobile side

Screenshots

If applicable, add screenshots to help explain your problem.

System information

• OS: ios and android
• expo 53 (latest), react-native 0.79.3

[grdsdev]

Hi, can you try out the version v2.50.1-next.6 and let me know if that fixes your issue?

Thanks.

[geoguide]

I think the client is issuing expired tokens

[cdekort]

2.50.0 is stable for us, 2.50.1 is breaking (postgres_changes, as well as broadcasting)