Fixed
Status Update
Comments
lu...@gmail.com <lu...@gmail.com> #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
lu...@gmail.com <lu...@gmail.com> #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"
lu...@gmail.com <lu...@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
lu...@gmail.com <lu...@gmail.com> #5
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
lu...@gmail.com <lu...@gmail.com> #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
na...@codeaurora.org <na...@codeaurora.org> #7
same
lu...@gmail.com <lu...@gmail.com> #8
SAME ! - Google can't do sth working in 100 percent?
lu...@gmail.com <lu...@gmail.com> #9
same issue - Google Play services out of date. Requires 3159100 but found 3158130
sv...@axis.com <sv...@axis.com> #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
na...@codeaurora.org <na...@codeaurora.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
qa...@gmail.com <qa...@gmail.com> #12
Same issue here.
qa...@gmail.com <qa...@gmail.com> #13
Same issue here. How can i fix this bug?
mi...@gmail.com <mi...@gmail.com> #14
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
ek...@google.com <ek...@google.com> #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.
ek...@google.com <ek...@google.com> #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
lu...@gmail.com <lu...@gmail.com> #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!!
lu...@gmail.com <lu...@gmail.com> #18
lu...@gmail.com <lu...@gmail.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.
gi...@appspot.gserviceaccount.com <gi...@appspot.gserviceaccount.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...
lu...@gmail.com <lu...@gmail.com> #21
Any ETA on this fix? Appreciate your reply.
is...@google.com <is...@google.com> #22
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.
Description
*************************************************************************
*** !!!! THIS BUG TRACKER IS FOR GERRIT CODE REVIEW !!!!
*** Do not submit bugs for chrome/android and issues with your company's
*** Gerrit setup here. Those issues belong in different issue trackers.
*************************************************************************
What steps will reproduce the problem?
1. Create a new change with PS1
2. Edit the commit locally, removing the last char of the Change-Id field at the bottom of the commit message
3. Upload the change and create PS2
What is the expected output?
PS2 should be rejected because the Change-Id is corrupted.
What do you see instead?
The PS2 is accepted into the change, creating a paradox where the PSs of a change have different Change-Ids, some of them are corrupted.
Please provide any additional information below.