Assigned
Status Update
Comments
gu...@gmail.com <gu...@gmail.com> #2
I notice the same issue and LogCat shows the following message:
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
ni...@chromium.org <ni...@chromium.org> #3
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
ss...@google.com <ss...@google.com> #4
me as well....
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
ri...@chromium.org <ri...@chromium.org> #5
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
gu...@gmail.com <gu...@gmail.com> #6
Having the same issue:
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
gu...@gmail.com <gu...@gmail.com> #7
same
ri...@chromium.org <ri...@chromium.org> #8
SAME ! - Google can't do sth working in 100 percent?
gu...@gmail.com <gu...@gmail.com> #9
same issue - Google Play services out of date. Requires 3159100 but found 3158130
gu...@gmail.com <gu...@gmail.com> #10
Having the same issure:
07-26 03:14:00.731: W/GooglePlayServicesUtil(2566): Google Play services out of date. Requires 3159100 but found 3136130
07-26 03:14:00.731: W/GooglePlayServicesUtil(2566): Google Play services out of date. Requires 3159100 but found 3136130
Description
Steps to reproduce the problem
Problem Description
This does not work
var abortable = new AbortController(); var { signal, } = abortable; var wss = new WebSocketStream("wss://0.0.0.0:8000", {signal}); var { readable, writable, } = await wss.opened.catch(console.error); readable.pipeTo(...); abortable.abort("reason");
This does work
readable.pipeTo(..., {signal}); abortable.abort("reason"); // Or // await writer.close(); // await writer.abort();
Summary
AbortController.abort() does not send close frame to WebSocketStream(url, {signal})
Custom Questions
Which component does this fall under?
Blink>Network
Does this work in other browsers?
Yes - This is just a Chrome problem
Additional Data
Category: API
Chrome Channel: Not sure
Regression: N/A