[Feature request]: Add pull token approach to Realtime

[grdsdev]

Feature request

To better align realtime with other libs (they all use a pull approach), let's:

• add an accessToken closure to the realtime client initialization;
• make SupabaseClient inject a method for pulling the access token from Auth.

Reference PR: supabase/supabase-swift#615

[arun-h]

Hello @grdsdev , I’d like to work on this issue

My approach is:
-Add an optional get_access_token: Callable[[], str] parameter when initializing the realtime client.
-Update the realtime client so it calls this function whenever it needs a token.
-Update Supabaseclient to inject a default method that fetches the current access token from auth.get_session().

This will mirror the approach taken in supabase/supabase-swift#615

Please let me know if you’d like any adjustments before I open a PR

[AnshikaCraftCode]

I think this is solvable with a relatively small, non-breaking change.
Instead of capturing the access token at Realtime client initialization, we could switch to a pull-based approach by introducing an access-token provider (closure/callback) that is invoked when the Realtime client connects or reconnects.
Concretely:
Realtime client accepts a get_access_token callable instead of a static token
SupabaseClient injects a default implementation that pulls from auth.get_session()
Static tokens can be wrapped in a lambda for backward compatibility
This would align Realtime with how other SDKs handle refreshed tokens and avoid stale auth state without requiring a broader refactor.

[Scarage1]

Hi everyone 👋
Thanks for the discussion — this makes sense and feels like a clean, non-breaking improvement.

I plan to implement a pull-based token approach by introducing an optional get_access_token: Callable[[], str] on the Realtime client, which will be invoked whenever the client connects or reconnects, instead of capturing a static token at initialization.

In SupabaseClient, I’ll inject a default implementation that pulls the latest access token from auth.get_session(). For backward compatibility, static tokens will be wrapped in a lambda so existing usage continues to work unchanged.

This should mirror the approach taken in supabase-swift#615 and align Realtime auth behavior with other SDKs while avoiding stale tokens.