Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / dart-lang/web_socket_channel issues and pull requests
#215 - Allow specifying a custom client for IOWebSockets
Pull Request -
State: closed - Opened by dudeofawesome over 2 years ago
- 1 comment
#214 - Report the specific reason(s) for 'WebSocket connection failed.'
Issue -
State: closed - Opened by farr64 over 2 years ago
- 1 comment
#213 - Unable to install web_socket_channel 2.2.0
Issue -
State: closed - Opened by niranjanglynk over 2 years ago
- 1 comment
#212 - websocket connection issue
Issue -
State: closed - Opened by Surajsahani28 over 2 years ago
- 1 comment
Labels: question
#211 - Custom http client
Pull Request -
State: closed - Opened by pavlov061356 over 2 years ago
- 3 comments
#210 - Error: Couldn't resolve the package 'web_socket_channel' in 'package:web_socket_channel/web_socket_channel.dart'.
Issue -
State: open - Opened by Reinoal over 2 years ago
- 1 comment
#209 - How to get event on socket connected
Issue -
State: open - Opened by UmeshChakre over 2 years ago
- 2 comments
#208 - Whow make a Broadcast for send a same message for all connect clients ?
Issue -
State: open - Opened by Luanfern over 2 years ago
#207 - IOS manually turn off cellular data, it takes a long time to trigger onDone
Issue -
State: open - Opened by cookie-session over 2 years ago
- 3 comments
#206 - Why can not connect Https ?
Issue -
State: open - Opened by Zasa-an almost 3 years ago
- 4 comments
#204 - Socket error is WebSocketChannelException: WebSocketChannelException: HttpException: Connection closed before full header was received, uri = http://192.168.1.9:8080
Issue -
State: open - Opened by maheshsuthar93 almost 3 years ago
- 6 comments
#202 - WebSocketChannelException: HttpException: Connection closed before full header was received, uri = http://192.168.10.30:3001
Issue -
State: open - Opened by i-am-ijaz almost 3 years ago
- 4 comments
#200 - In web_socket_channel connection can't set header for authentication
Issue -
State: open - Opened by anjojy about 3 years ago
- 3 comments
#199 - channel.sink.add not support binary message in web?
Issue -
State: closed - Opened by bajizhh about 3 years ago
- 1 comment
#194 - Unable to send data to server
Issue -
State: closed - Opened by ericel about 3 years ago
- 1 comment
#193 - how to catch error response on channel.sink.add?
Issue -
State: open - Opened by b14cknc0d3 about 3 years ago
- 9 comments
#192 - Attempting to close a websocket from inside of Flutter for web throws a stack trace
Issue -
State: closed - Opened by domesticmouse about 3 years ago
- 2 comments
Labels: question
#190 - Listening for incomming messages lags on Android hardware.
Issue -
State: closed - Opened by robertpiosik about 3 years ago
- 3 comments
#189 - WRONG_VERSION_NUMBER when I use wss instead of https
Issue -
State: open - Opened by dungnc about 3 years ago
- 5 comments
#187 - Add HtmlWebSocketChannel.innerWebSocket
Pull Request -
State: closed - Opened by chirag729 over 3 years ago
- 9 comments
Labels: cla: yes
#186 - Websocket disconnects for no reason on flutter web
Issue -
State: open - Opened by arualana over 3 years ago
- 6 comments
#185 - close() but not really closed ?
Issue -
State: open - Opened by garyng2000 over 3 years ago
- 6 comments
#182 - How can I catch "WebSocketException: Connection to '***#' was not upgraded to websocket" exception
Issue -
State: closed - Opened by duhanbalci over 3 years ago
- 7 comments
#181 - WebSocketChannelException: WebSocket connection failed
Issue -
State: closed - Opened by moluopro over 3 years ago
- 4 comments
Labels: type-question
#178 - Bad response 'Sec-WebSocket-Accept' header
Issue -
State: closed - Opened by 651619114 over 3 years ago
- 1 comment
#166 - [Ping Interval] WebSocketChannel.connect with pingInterval
Issue -
State: open - Opened by Kainanchen over 3 years ago
- 4 comments
#164 - Connection to {MY_SOCKET_URL} was not upgraded to websocket
Issue -
State: closed - Opened by lionuncle over 3 years ago
- 7 comments
Labels: question
#159 - Unsupported operation: Platform._version - on Flutter 2.0.0 Web
Issue -
State: closed - Opened by wilk3ns over 3 years ago
- 4 comments
Labels: question
#157 - 'Sec-WebSocket-Accept' is the wrong length
Issue -
State: closed - Opened by vivihu over 3 years ago
- 1 comment
#129 - Get connection state after connect
Issue -
State: open - Opened by sturmf almost 4 years ago
- 2 comments
#125 - Bad state: Stream has already been listened to.
Issue -
State: open - Opened by carlfost about 4 years ago
- 2 comments
#122 - How to handle the websocket stream, when lockscreen is activated
Issue -
State: closed - Opened by KevinRohn over 4 years ago
- 1 comment
#105 - modify http, support wss:// and check cert in the app
Pull Request -
State: closed - Opened by kecson over 4 years ago
- 6 comments
Labels: cla: yes
#101 - How to detect the socket connection status?
Issue -
State: open - Opened by sachin052 over 4 years ago
- 3 comments
#94 - subscribe websocket channel topic
Issue -
State: open - Opened by jzDeveloper over 4 years ago
- 1 comment
#93 - WebSocketChannelException: WebSocketChannelException: HandshakeException: Handshake error in client CERTIFICATE_VERIFY_FAILED: unable to get local issuer certificate(handshake.cc:354))
Issue -
State: open - Opened by jacky-yanglei over 4 years ago
- 6 comments
#89 - Wss error
Issue -
State: open - Opened by aymanmanee3 almost 5 years ago
- 2 comments
#89 - Wss error
Issue -
State: open - Opened by aymanmanee3 almost 5 years ago
- 2 comments
#86 - how to use proxy?
Issue -
State: closed - Opened by philos3 almost 5 years ago
- 7 comments
#85 - Added IOWebSocketChannel.ready field and timeout parameter
Pull Request -
State: closed - Opened by KammererTob almost 5 years ago
- 22 comments
Labels: cla: yes
#79 - An exception if the server sends message when connecting
Issue -
State: closed - Opened by Claus1 about 5 years ago
- 3 comments
#76 - My websocket app work on debug mode but doesn't on release mode
Issue -
State: closed - Opened by hariangr about 5 years ago
- 8 comments
#63 - How to use self signed certs?
Issue -
State: open - Opened by winter91 over 5 years ago
- 4 comments
#61 - Lack of ability to configure connection timeouts
Issue -
State: open - Opened by nailgilaziev over 5 years ago
- 18 comments
#57 - Header Error => Connection closed before full header was received.
Issue -
State: open - Opened by MertTutsak over 5 years ago
- 6 comments
#56 - How to reconnect when the client is offline?
Issue -
State: closed - Opened by TomLiu-GitHub over 5 years ago
#55 - How to reconnect when the client is offline?
Issue -
State: closed - Opened by TomLiu-GitHub over 5 years ago
#54 - How to reconnect when the client is offline?
Issue -
State: closed - Opened by TomLiu-GitHub over 5 years ago
#53 - How to reconnect when the client is offline?
Issue -
State: closed - Opened by TomLiu-GitHub over 5 years ago
#52 - How to reconnect when the client is offline?
Issue -
State: closed - Opened by TomLiu-GitHub over 5 years ago
#51 - How to reconnect when the client is offline?
Issue -
State: closed - Opened by TomLiu-GitHub over 5 years ago
#50 - How to reconnect when the client is offline?
Issue -
State: open - Opened by TomLiu-GitHub over 5 years ago
- 2 comments
#42 - Responding to ping event
Issue -
State: open - Opened by gurgenDP over 5 years ago
- 5 comments
#40 - How to detect channel disconnected (can not listen cause message will duplicated)
Issue -
State: open - Opened by lucasjinreal almost 6 years ago
- 37 comments
#38 - some errors can't be handled in IOWebSocketChannel.connect
Issue -
State: open - Opened by SteveAlexander almost 6 years ago
- 10 comments
#25 - Add a WebSocketChannel.ready field
Issue -
State: closed - Opened by nex3 over 6 years ago
- 18 comments
#16 - An ability to get state of connection
Issue -
State: open - Opened by gradddev over 6 years ago
- 42 comments
Labels: type-enhancement