You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
WebSocket message is received on VM & JS environments but not on WASM.
i.e. webSocketClient.stream.json or webSocketClient.stream.text or webSocketClient.stream.bytes doesn't emit any data when flutter app is compiled to WebAssembly
Expected behavior
WebSocket message is received.
Desktop (please complete the following information):
Fixed in 2.0 (branch rewrite, ships with 2.0.0-dev.1). The browser transport was rewritten on package:web and dart:js_interop, and messages are received under dart2wasm: the full browser suite, including end-to-end tests against a real server (text, binary, JSON, large and fragmented messages), runs in Chrome under both dart2js and dart2wasm on every CI run (web_server_test.dart, web_transport_test.dart).
Activity
PlugFox commentedon Oct 15, 2024
Yes, wasm is a pretty fresh compilation target; I'll take a look at that problem in the near future.
PlugFox commentedon Nov 12, 2026
Fixed in 2.0 (branch
rewrite, ships with 2.0.0-dev.1). The browser transport was rewritten onpackage:webanddart:js_interop, and messages are received under dart2wasm: the full browser suite, including end-to-end tests against a real server (text, binary, JSON, large and fragmented messages), runs in Chrome under both dart2js and dart2wasm on every CI run (web_server_test.dart, web_transport_test.dart).