Conversation
… before flushing send buffer
@supabase/auth-js
@supabase/functions-js
@supabase/postgrest-js
@supabase/realtime-js
@supabase/storage-js
@supabase/supabase-js
commit: |
filipecabaco
approved these changes
Feb 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the current behavior?
On React Native / Expo, the auth
accessTokencallback reads from async storage (e.g.expo-secure-store). Whensubscribe()is called before the token has resolved, thephx_joinpayload is captured with noaccess_token. The stale join message is buffered, and when_onConnOpen()fires it flushes the buffer — sending the token-less join to the server.The server accepts the join but cannot evaluate RLS policies without a token, so
postgres_changesevents are silently filtered out. The channel appears subscribed but no data arrives.On browsers this never happens because
localStorage.getItem()is synchronous, so the token is always available whensubscribe()snapshots the join payload.Fixes #1461
Related: #1477, #1725
What is the new behavior?
In
_onConnOpen(), after the auth promise resolves:joinPushpayload with the now-availableaccessTokenValuejoiningstateOn browsers this is a no-op — the token was already present at
subscribe()time.