Fixed
Status Update
No update yet.
Comments
ik...@gmail.com
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
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
va...@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
ik...@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
ik...@gmail.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
ik...@gmail.com
same
ik...@gmail.com
SAME ! - Google can't do sth working in 100 percent?
ik...@gmail.com
same issue - Google Play services out of date. Requires 3159100 but found 3158130
bo...@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
kh...@chromium.org
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
bo...@chromium.org
Same issue here.
kh...@chromium.org
Same issue here. How can i fix this bug?
kh...@chromium.org
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
bo...@chromium.org
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.
bo...@chromium.org
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
kh...@chromium.org
Same page here!
07-31 22:47:40.277: W/GooglePlayServicesUtil(1009): Google Play services out of date. Requires 3159100 but found 3158130
Thing is: we work under timelines too, and we need this fix quick! I cannot go wondering around asking for cellphones all over the place... I used to have this fixed with my emulators!!
07-31 22:47:40.277: W/GooglePlayServicesUtil(1009): Google Play services out of date. Requires 3159100 but found 3158130
Thing is: we work under timelines too, and we need this fix quick! I cannot go wondering around asking for cellphones all over the place... I used to have this fixed with my emulators!!
kh...@chromium.org
sa...@google.com
The Play Services team knows about this issue and is working on it with a high priority. The fix for this will go in the same emulator image in the same timeframe. Sorry I'm being vague about when it'll go out; I don't want to tell you something and then have us miss it. I'll update this bug when I know more.
kx...@gmail.com
Just would like to add that we are experiencing this on device as well, not just in AVD. Not sure if that matters...
va...@gmail.com
Any ETA on this fix? Appreciate your reply.
bo...@chromium.org
There's no ETA yet. I think a new version of the Google Play Services add-on in the SDK manager is going out today, but this doesn't help the issue of needing to update the emulator system images.
bu...@chops-service-accounts.iam.gserviceaccount.com
Any update on this?
Any chance you could put a note in the tutorial/setup documentation as it is infuriating (not to mention a waste of time) to follow steps exactly as described and not get something working. Resorting to Stack Overflow to find a load of hacks (and a lot of incorrect answers) for manually installing the required .apks and finally a link here to see that the issue is at least 3 weeks old with no target fix date.
Any chance you could put a note in the tutorial/setup documentation as it is infuriating (not to mention a waste of time) to follow steps exactly as described and not get something working. Resorting to Stack Overflow to find a load of hacks (and a lot of incorrect answers) for manually installing the required .apks and finally a link here to see that the issue is at least 3 weeks old with no target fix date.
va...@gmail.com
I agree, please update the documentation while it is not working.
bo...@chromium.org
Agreed on updating the documentation. I wasted two days on this issue and it pains me to see it repeated Ad nauseam.
bo...@chromium.org
I lost hours on this problem thinking it was my fault.
Is ridiculous that a company like google do shit like that.
Is ridiculous that a company like google do shit like that.
va...@gmail.com
This should go out today.
va...@gmail.com
@howardb Thank Jah!
ik...@gmail.com
I just updated Android in Eclipse via the SDK Manager. The first launch of my previously working application on the emulator (using Google APIs - API Level 17) generated the following error:.
GooglePlayServicesUtil(1105): Google Play services out of date. Requires 3159100 but found 3136130
Only using a new Emulator (using Google APIs - API Level 18) does the application run.
Will the older API Level 17 be updated with a new Google Play services?
GooglePlayServicesUtil(1105): Google Play services out of date. Requires 3159100 but found 3136130
Only using a new Emulator (using Google APIs - API Level 18) does the application run.
Will the older API Level 17 be updated with a new Google Play services?
va...@gmail.com
Sorry, we're only committing to keeping the latest API up-to-date.
[Deleted User] <[Deleted User]>
How to fix this?
Google Play services out of date. Requires 3225100 but found 3136130
Google Play services out of date. Requires 3225100 but found 3136130
bo...@chromium.org
gone mad with the problem:
Google Play services out of date. Requires 3264100 but found 3225136
Plz somebody give some fix...
Google Play services out of date. Requires 3264100 but found 3225136
Plz somebody give some fix...
bo...@chromium.org
After updating my sdk to API 18, my AVD doesn't play any sound.
kx...@gmail.com
Tested on 82.0.4083.0 dev
With this urlhttps://techcommunity.microsoft.com/t5/discussions/top-feedback-summary-for-february-11/m-p/1167413
It changed from no-flick to white flick on my PC
(stable don't have that but only flick when I pass home/end key) Now just scroll the scroll bar can make white block appear easily on dev version
But the black block on other website don't appear now. (don't test it strictly)
Hey. But I found that on current stable version. The black block is more easier to trigger. It even triggerable on the upper area of screen!!!!!
With this url
It changed from no-flick to white flick on my PC
(stable don't have that but only flick when I pass home/end key) Now just scroll the scroll bar can make white block appear easily on dev version
But the black block on other website don't appear now. (don't test it strictly)
Hey. But I found that on current stable version. The black block is more easier to trigger. It even triggerable on the upper area of screen!!!!!
bo...@chromium.org
Same here...
The version of emulator (API 18, Google APIs rev 2) running Google Play services version 3.2.25 but the Play Client Library is of version 3.2.64 (rev 11).
Can we just get somewhere the older version of client library?
Or when you will update emulator with the latest Play services?
The version of emulator (API 18, Google APIs rev 2) running Google Play services version 3.2.25 but the Play Client Library is of version 3.2.64 (rev 11).
Can we just get somewhere the older version of client library?
Or when you will update emulator with the latest Play services?
bo...@chromium.org
The issue is that we've paused rollout of the latest version of the Play Services APK, so many of those building with an updated client library can't update the APK on their devices. The plan is to roll back v11 of the client library until we get everything hammered out.
Version incompatibilities with the emulator are a slightly different issue (since the emulator has the APK baked in and can't update it); I'm investigating that.
Version incompatibilities with the emulator are a slightly different issue (since the emulator has the APK baked in and can't update it); I'm investigating that.
sa...@microsoft.com
I've purged version 11 temporarily from the servers as the issue gets fixed.
Note that users who installed r11 need to:
1- Open sdk manager, let it refresh its remote list.
2- Select Google Play Service v11 => Delete package
3- They should see v10 which they can install instead.
Note that users who installed r11 need to:
1- Open sdk manager, let it refresh its remote list.
2- Select Google Play Service v11 => Delete package
3- They should see v10 which they can install instead.
kx...@gmail.com
I followed the steps to delete the r11 package, but when I refresh the SDK manager, it still stays 11, not 10. Still getting the "Google Play services out of date" message in LogCat. Thanks in advance!
bo...@chromium.org
Preparing to install archives
Downloading Google Play services, revision 11
Download interrupted: URL not found.
Done. Nothing was installed.
What is this ?
The above message is shown while downloading Google Play Services, rev 11 through SDK manager.
Downloading Google Play services, revision 11
Download interrupted: URL not found.
Done. Nothing was installed.
What is this ?
The above message is shown while downloading Google Play Services, rev 11 through SDK manager.
kx...@gmail.com
#36 => Thank you mate!
is...@google.com
To see Play Services v10 in your SDK manager, you may need to delete the .android/cache directory in your home directory and restart SDK manager.
Description
Example URL:
Steps to reproduce the problem:
1. Open
2. Scroll up and down rapidly (ideally using a scroll wheel)
3. View the centered-content, the cards with the product images
Other URLs where the bug is reproducible:
(any URL with a long scrolling section, where your scroll speed outpaces Chrome's repainting)
What is the expected behavior?
After the website is loaded & fully rendered, scrolling up and down should not cause the page to repaint.
Once it's loaded, users should be able to scroll up & down without the page partially re-painting.
What went wrong?
As you scroll down or up quickly, the page content disappears (even though it's already been painted once). If you slow down your scrolling, the page is repainted in time and there are no issues.
If you maintain the high scroll speed, the entire page can disappear completely.
Does it occur on multiple sites: Yes
Is it a problem with a plugin? No
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: 80.0.3987.106 Channel: stable
OS Version: 10.0
Flash Version:
Bisect already completed (log attached). Important note: the issue is LESS prominent in Chromium vs Chrome, but it exists in BOTH. It's much worse on Chrome Stable, however.
Bisect:
Known Good = 721354 (video:
First Known Bad = 721365 (video:
Changelog URL =
Also, for good measure, Stable | Very Bad = 722274 (video:
//
This issue is NOT present on Firefox 72, but is present in other Chromium browsers (e.g., Edge Chromium-based Stable 80.0.361.50).
Curiously: both bisects are reported as Chromium 80.0.3986.0, BUT have different branches. I'm no developer, but the *probable* issue probably started here:
//
I *cannot* reproduce this issue on a 120 Hz display connected to a dedicated GPU (NVIDIA GT 710). All tests above that exhibit the problem are on from an Intel i5-8600K iGPU (Intel UHD Graphics 630) connected via HDMI to a Dell SE2416H 24" 60Hz 1080p monitor running at 100% DPI.
Full system specifications:
CPU: i5-8600K (iGPU = Intel UHD Graphics 630)
Motherboard: ASRock Z370-Fatal1ty mini-ITX
Monitor: Dell SE2416H 24", 60 Hz, 1080p, connected via HDMI
Windows 10 Pro x64 1909 (18363.657)
//
On a final note, I've found a few other bugs with somewhat similar problems, but wildly different bisects or much different symptoms. Please mark this as a duplicate if this bug with this bisect has already been reported; my sincere apologies if that is true!