• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / supabase-swift / 44309027756
96%

Build:
DEFAULT BRANCH: main
Ran 18 Nov 2026 01:06PM UTC
Jobs 1
Files 223
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

18 Nov 2026 12:58PM UTC coverage: 96.16% (+0.01%) from 96.148%
44309027756

push

github

web-flow
fix(realtime)!: treat a nil access token after a real one as "no user" (#1865)

* fix(realtime)!: treat a nil access token after a real one as "no user"

A standalone RealtimeClient kept the previous user's token when its
accessToken callback returned nil, so a signed-out user kept channel
access until the token expired (SWIFT-V3-004).

A nil result now clears the stored token and its expiry. Later joins
carry no access_token, so the server uses the socket's API key, and
joined channels get the apikey header's value (the server ignores a
null access_token push). httpSend sends only apikey. A callback that
throws or times out still keeps the token: the core now gets a separate
tokenFetchFailed event for that case.

SupabaseClient's Realtime callback returns the API key when there is no
session, the key it already pushes at sign-out, so its wire behavior
does not change.

BREAKING CHANGE: in a standalone RealtimeClient, an accessToken callback
that returns nil now clears the stored token instead of keeping it, and
httpSend drops an Authorization header from `headers` in that case.

Fixes SDK-3106

* fix(realtime): send the API key back to a joining channel that got a newer token

A channel that joined with one token and then got another before its join
reply skipped the next push of its join token, so the server kept the
newer token. The channel now tracks the last token it sent, not only the
one in its join. Also fixes the Auth.md httpSend note for a nil token, and
updates the integration test for the clock setter from main.

* chore: remove a stray Supabase CLI lease file

* fix(supabase): give Realtime its own header token when no user is signed in

With no session, the Realtime callback and the .signedOut push sent
supabaseKey. A client that overrides Realtime's Authorization header
(for example, a service-role client that gives Realtime the anon key)
then joined with supabaseKey. Both now use the bearer token of the merged
Realtime headers, which i... (continued)

55 of 57 new or added lines in 8 files covered. (96.49%)

3 existing lines in 1 file now uncovered.

16502 of 17161 relevant lines covered (96.16%)

665672.37 hits per line

Uncovered Changes

Lines Coverage ∆ File
2
93.18
-0.46% Sources/Realtime/RealtimeClient+Connection.swift

Coverage Regressions

Lines Coverage ∆ File
3
97.52
-2.48% Sources/Helpers/JSONValue/JSONValue.swift
Jobs
ID Job ID Ran Files Coverage
1 44309027756.1 18 Nov 2026 01:06PM UTC 223
96.16
GitHub Action Run
Source Files on build 44309027756
  • Tree
  • List 223
  • Changed 12
  • Source Changed 11
  • Coverage Changed 8
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #44309027756
  • 554ed9f8 on github
  • Prev Build on main (#44300535269)
  • Next Build on main (#44311596979)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc