Auto reconnect loses subscription to postgres_changes
events
#213
Labels
bug
Something isn't working
postgres_changes
events
#213
Bug report
Describe the bug
The
auto_reconnect
feature, which was fixed in PR #203, is not functioning as expected. When the connection to the realtime server is lost and reconnected usingauto_reconnect = true
, the client successfully rejoins the channel but does not resubscribe to thepostgres_changes
events.To Reproduce
An extracted version of the code setup:
Expected behavior
After the connection is automatically reestablished, all postgres_changes events should be resubscribed.
Log
2024-09-30T13:08:13.712427114Z
nopostgres_changes
are sent to the realtime server. On the first connect at2024-09-30T13:05:21.388617410Z
they have been sent.INFO: Channel phoenix not found
message appears repeatedly (is this related to the heartbeat?). It becomes a bit overwhelming as it floods the logs. I'm connecting to a Supabase cloud instance. Is there any configuration I need to set up to ensure this channel exists?System information
The text was updated successfully, but these errors were encountered: