Obsolete
Status Update
No update yet.
Comments
sa...@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
sa...@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"
nh...@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
aa...@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
[Deleted User] <[Deleted User]>
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
aa...@gmail.com
same
aa...@gmail.com
SAME ! - Google can't do sth working in 100 percent?
sa...@chromium.org
same issue - Google Play services out of date. Requires 3159100 but found 3158130
ma...@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
ba...@gmail.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
aa...@gmail.com
Same issue here.
[Deleted User] <[Deleted User]>
Same issue here. How can i fix this bug?
sa...@chromium.org
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
aa...@gmail.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.
ba...@gmail.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
aa...@gmail.com
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!!
aa...@gmail.com
ma...@chromium.org
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.
aa...@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...
ma...@chromium.org
Any ETA on this fix? Appreciate your reply.
sv...@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.
aa...@gmail.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.
[Deleted User] <[Deleted User]>
I agree, please update the documentation while it is not working.
zh...@chromium.org
Agreed on updating the documentation. I wasted two days on this issue and it pains me to see it repeated Ad nauseam.
el...@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.
is...@google.com
This should go out today.
Description
Steps to reproduce the problem:
1. Web application login
2. Scripts fetched - ERR timeout seen here here for different scripts each time
3. Subsequent XMLHttpRequest errors seen after
What is the expected behavior?
What went wrong?
When the web application loads, a bunch of scripts are fetched. Everytime, a random script fails to be queried. It errors out with the following error:
Failed to load resource: net::ERR_TIMED_OUT ..
Right after that, the subsequent XHR calls fail with the following error:
DOMException: Failed to execute 'send' on XMLHttpRequest: Failed to load '<the same filename it ERR_TIMED_OUT out on>'
All of this has been working perfectly for the past few years and all of a sudden in the past week, we have been observing this issue.
Things to note:
1. Works perfectly on all other browsers - Firefox, Safari, Edge
2. No Proxy networks
3. The request does not seem to even reach the server with chrome
4. It is not a cross-domain request
5. This is the latest version of chrome
6. Tried clearing entire cache, browsing data; Switched off hardware acceleration; Enabled #allow-sync-xhr-in-page-dismissal flag to just check; Cleared IndexedDb as well - Nothing helped.
Looking to hear back soon. It is pretty urgent. Thanks in advance.
Did this work before? Yes
Chrome version: 80.0.3987.132 Channel: stable
OS Version: OS X 10.14.6
Flash Version:
Works in the current version of Canary - Version 82.0.4085.4 (Official Build) canary (64-bit)