Skip to content

Reproducer: Websocket emits messages events even after close is called - #59287

Open
davidliu wants to merge 1 commit into
react:mainfrom
davidliu:websocket-close-reproducer
Open

davidliu wants to merge 1 commit into
react:mainfrom
davidliu:websocket-close-reproducer

Conversation

@davidliu

@davidliu davidliu commented Oct 21, 2026 •

Copy link
Copy Markdown

Summary:

Reproducer for #59289 that shows messages being emitted even after Websocket.close() has been called.

Not for merging

Changelog:

[INTERNAL] - Reproducer for Websocket message behavior after close()

Test Plan:

Open the Playground example in RNTester, observe logs on screen or through console logs:

Expected:

close() called, readyState=2
onclose code=...

Actual:

close() called, readyState=2
message after close(): "Request served by ...", readyState=2
message after close(): "hello", readyState=2
onclose code=...

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Oct 21, 2026
@facebook-github-tools facebook-github-tools Bot added the Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team. label Oct 21, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant