Obsolete
Status Update
Comments
mp...@gmail.com <mp...@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
ph...@chromium.org <ph...@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"
rs...@chromium.org <rs...@chromium.org> #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
[Deleted User] <[Deleted User]> #5
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
mp...@gmail.com <mp...@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
[Deleted User] <[Deleted User]> #7
same
sa...@chromium.org <sa...@chromium.org> #8
SAME ! - Google can't do sth working in 100 percent?
sw...@chromium.org <sw...@chromium.org> #9
same issue - Google Play services out of date. Requires 3159100 but found 3158130
ma...@chromium.org <ma...@chromium.org> #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
da...@chromium.org <da...@chromium.org> #11
API 18 (4.3) same issue
07-26 03:54:03.303: W/GooglePlayServicesUtil(1207): Google Play services out of date. Requires 3159100 but found 3158130
07-26 03:54:03.303: W/GooglePlayServicesUtil(1207): Google Play services out of date. Requires 3159100 but found 3158130
mm...@chromium.org <mm...@chromium.org> #12
Same issue here.
va...@chromium.org <va...@chromium.org> #13
Same issue here. How can i fix this bug?
mp...@gmail.com <mp...@gmail.com> #14
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
ma...@chromium.org <ma...@chromium.org> #15
Thanks for the update @sbarta. It is good that you are keeping us informed. This is a very critical and blocking bug for anyone developing with maps.
is...@google.com <is...@google.com> #16
FYI also getting same with PlusClient sign in, so this is not just a maps issue:
ConnectionResult.SERVICE_VERSION_UPDATE_REQUIRED
07-30 12:35:50.059: W/GooglePlayServicesUtil(16054): Google Play services out of date. Requires 3159100 but found 1013
ConnectionResult.SERVICE_VERSION_UPDATE_REQUIRED
07-30 12:35:50.059: W/GooglePlayServicesUtil(16054): Google Play services out of date. Requires 3159100 but found 1013
Description
Example URL:
Steps to reproduce the problem:
1. Have any web server with self-signed or otherwise untrusted cert, with http keep-alive enabled.
2. Make many XHR requests (GET and POST) at a time from a Chrome client, Windows/Mac/Linux/Android is all the same
I originally discovered this issue while working on a router with latest OpenWRT...
I have a spare router with nothing connected to it that I have set up for anyone to quickly take a look at the problem in real-time. SSH is also available on port 22. Web server config file is '/etc/config/uhttpd'. Ports 80 and 443 are open but HTTP still redirects to HTTPS for some reason.
https://[2601:585:4300:7da1:c66e:1fff:fe08:b5ac]/cgi-bin/luci/
password is "chromedev"
What is the expected behavior?
The security exception or "interstitial" of allowing the page to load should also allow the use of the self-signed cert for all subsequent requests, (and it does when HTTP keep-alive is off on the server).
Firefox (for certain) and probably every other browser does not have this issue. When I try the same thing on Firefox, there is a security warning, and bypassing it allows all resources to load perfectly fine over persistent HTTPS connections.
What went wrong?
Either
A. Performance is horrible and every subsequent request bombs and requires a new connection, which then bombs on the next request, or
B. A significant amount of the requests eventually time out
Did this work before? No
Chrome version: 80.0.3987.132 Channel: stable
OS Version: 10.0
Flash Version:
I have tried analyzing the connections with chrome://net-export and the respective tool to read the output but nothing there seems to be useful.