supabase / supabase-swift / 28864589364

83%

Build Type

push

github

Committed by web-flow

Commit Message

fix(realtime): keep current access token when token fetch fails in setAuth (#1077)

* fix(realtime): keep current access token when token fetch fails in setAuth

setAuth used try? on the accessToken callback, so a transient failure
(e.g. a network error while Auth refreshes the session) produced a nil
token that overwrote the stored one and pushed access_token: null to
every subscribed channel. Since sendHeartbeat calls setAuth on every
tick, a single failed refresh could drop RLS-authorized subscriptions.
Keep the last known token and skip the push when the callback throws,
matching realtime-js where a rejected accessToken() propagates instead
of sending null.

* test(realtime): assert setAuth pushes no null token to channels on fetch failure

* Update Sources/RealtimeV2/RealtimeClientV2.swift

Co-authored-by: Guilherme Souza <ogrsouza@gmail.com>

---------

Co-authored-by: Guilherme Souza <ogrsouza@gmail.com>

Coverage Stats

6 of 6 new or added lines in 1 file covered. (100.0%)

6 existing lines in 2 files now uncovered.

7824 of 9402 relevant lines covered (83.22%)

37.38 hits per line