Status Update
No update yet.
Comments
st...@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
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"
pe...@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
st...@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
sw...@chromium.org
same
st...@gmail.com
SAME ! - Google can't do sth working in 100 percent?
[Deleted User] <[Deleted User]>
same issue - Google Play services out of date. Requires 3159100 but found 3158130
ke...@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
ke...@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
to...@chromium.org
Same issue here. How can i fix this bug?
ha...@google.com
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
is...@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.
Description
Chrome Version : <from chrome://version/>
OS : <OS version>
What steps will reproduce the problem?
I am trying to debug an issue in my website. My front-end is deployed to 1 server and the back-end is deployed to a different server. We have CORS setup to enable calls from the front-end to the back-end.
The back-end has a failure which results in a 500 response to the browser for OPTIONS calls
What is the expected result?
The "Network" Tab shows the OPTIONS call failing with a 500 (or maybe the GET call like FireFox does).
What happens instead?
Tn the "Network" tab I see the GET call failed. No indication why. No headers from the response. There is a failure message to the console and with the following message: Access to XMLHttpRequest at 'API_URI' from origin 'DOMAIN' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
You can help us a lot by creating a minimal, reproducible examplehttps://stackoverflow.com/help/minimal-reproducible-example ), e.g. on
(
glitch.com, and/or attaching a screenshot or recording of the issue!