Status Update
No update yet.
Comments
sw...@chromium.org
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
jh...@chromium.org
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
jh...@chromium.org
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
da...@gmail.com
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
do...@thumbtack.com
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]>
same
jh...@chromium.org
SAME ! - Google can't do sth working in 100 percent?
ma...@chromium.org
same issue - Google Play services out of date. Requires 3159100 but found 3158130
ae...@chromium.org
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
do...@thumbtack.com
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
bm...@chromium.org
Same issue here.
ha...@google.com
Same issue here. How can i fix this bug?
is...@google.com
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
pe...@google.com
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.
pe...@google.com
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
Steps to reproduce the problem:
1. Visit
2. Open DevTools console
3. Visit "Example 1" in the reproduction. Notice that the First Input Delay is slow when simulating touch devices.
4. Visit "Example 2" in the reproduction. Notice that the First Input Delay is fast for touch and non-touch devices. This example doesn't use negative margins.
5. Visit "Example 3" in the reproduction. Notice that the First Input Delay is fast for touch and non-touch devices. This example, like "Example 1", uses negative margins. But the negative margin value is small enough to not cause it to be slow on touch devices.
What is the expected behavior?
The First Input Delay speed is fast for touch and non-touch devices on all 3 examples.
What went wrong?
The First Input Delay is slow when a page uses negative margins and the user is on a touch device.
Did this work before? N/A
Does this work in other browsers? N/A
Chrome version: 87.0.4280.88 Channel: stable
OS Version: OS X 10.15.7
Flash Version: