calls to supabaseListener.subscribe() very slow to reconnect

[paul-brenner]

Recently I'm seeing that it can take up to 60 seconds for supabaseListener.subscribe() to complete. I just confirmed this is still true on v2.21.0.

This didn't happen previously so I'm trying to chase down whether it is a change in supabase or if I'm doing something wrong in my implementation. The part on my side I'm suspicious of is that I don't know what the best practice is for actively disconnecting/reconnecting.
Should I:

1. Call .unsubscribe() when my app goes into the background and then calling .subscribe() when it becomes active again
2. Do nothing when the app goes into the background, when it becomes active check if .status != .subscribed and only call .subscribe if that is the case
3. It doesn't matter

I opened a ticket with support because I was also seeing this in the realtime logs, so sorry if this is creating a dupe. The log messages look like:
"UnknownError: RPC call error" and "ErrorOnRpcCall: %{\n error: {:error, {:erpc, :timeout}},\n mod: Realtime.Tenants.Connect,\n func: :connect,\n target: :"realtime@2600:1f10:4c1b:cc02:d97a:cd4d:6bf:bc61"\n}"

[grdsdev]

Hi @paul-brenner

Regarding reconnecting taking too long to complete, I need to check with the backend team. Can you share the ticket ID so I can follow up internally with them?

About best practice for reconnecting, I'd recommend you do option 2, check if status != subscribed and call subscribe.

I plan to implement in the library the logic for automatically handling reconnection logic in case of background/foreground and also loss of internet connection, to have a robust socket connection.

Issues for tracking such changes:

• [Realtime] handle connection when app changes between background/foreground state #595
• [Realtime] auto-reconnect socket and channels when internet connection is reestablished #579

[paul-brenner]

Thanks!
The ticket id is: 15893104508

I'll try what you recommended and see if it helps.

[paul-brenner]

This issue seems to be resolved for me now though I can't say if it was the recommended changes or improvements on the supabase server side