fix(realtime): send heartbeat for initial connection error#1746
Merged
Conversation
d33afe6 to
e2db0f0
Compare
filipecabaco
previously approved these changes
Jan 22, 2026
e2db0f0 to
7fb75c7
Compare
filipecabaco
approved these changes
Jan 22, 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
3 participants
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.
Moved from: supabase/realtime-js#507
Author: @bhavyasaggi
What kind of change does this PR introduce?
Add missing heartbeat on connection error.
What is the current behavior?
If the Supabase instance is unreachable during initial realtime connection, there is no status update available.
What is the new behavior?
Trigger a heartbeat-callback with 'error' on connection-error.