Status Update
Comments
su...@chromium.org <su...@chromium.org> #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
ge...@chromium.org <ge...@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"
as...@gmail.com <as...@gmail.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
sh...@chromium.org <sh...@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
ja...@chromium.org <ja...@chromium.org> #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]> #8
SAME ! - Google can't do sth working in 100 percent?
ya...@chromium.org <ya...@chromium.org> #9
same issue - Google Play services out of date. Requires 3159100 but found 3158130
[Deleted User] <[Deleted User]> #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
ds...@chromium.org <ds...@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
bm...@chromium.org <bm...@chromium.org> #13
Same issue here. How can i fix this bug?
ds...@chromium.org <ds...@chromium.org> #14
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
ds...@chromium.org <ds...@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.
ja...@chromium.org <ja...@chromium.org> #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
bm...@chromium.org <bm...@chromium.org> #17
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!!
is...@google.com <is...@google.com> #18
pe...@google.com <pe...@google.com> #19
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.
pe...@google.com <pe...@google.com> #20
Just would like to add that we are experiencing this on device as well, not just in AVD. Not sure if that matters...
Description
Steps to reproduce the problem:
1. In Dev Tools > Sources > Overrides, add a folder that contains a large binary. The one I tested with was 1.5GB - the bigger the better (probably) when reproducing this.
2. Un-check the "Enable Local Overrides" box.
3. Attempt to use the global search in the dev tools (CTRL+SHIFT+F) to search for any phrase.
What is the expected behavior?
At the very least, the local overrides should not be searched because they are not enabled.
I would also expect that the search shouldn't try to load entire files into memory if they're too big. Either read them in chunks, or ignore files over a certain (configurable?) size entirely.
Or, ignore files that don't look like text files, but this is probably harder to do.
What went wrong?
The search hangs, and eventually the whole devtools crash. The Chrome task manager shows that the dev tools memory usage spiked to around 2GB before crashing.
I suspect the the search is trying to load the entire binary file into memory all at once.
Did this work before? No
Chrome version: 74.0.3729.169 Channel: stable
OS Version: 10.0
Flash Version:
Arguably, the huge binary file shouldn't have been there in the first place. It was a local (.gitignore'd) output of some commands I was running. However, I went for quite a long time (6 months+) of my devtools search being broken because I could never figure out what was causing this. I figured it was a regression in Chrome that would be fixed eventually.
However, a crash is a crash, and I don't think the devtools should be assuming that every file in a local overrides folder is something that can be read into memory in its entirety. It would be great if there were some level of safeguards to prevent crashes like this.