Obsolete
Status Update
No update yet.
Comments
ch...@google.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
vs...@google.com
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
am...@gmail.com
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
vs...@google.com
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
am...@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
am...@gmail.com
same
am...@gmail.com
SAME ! - Google can't do sth working in 100 percent?
ks...@google.com
same issue - Google Play services out of date. Requires 3159100 but found 3158130
am...@gmail.com
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
am...@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
am...@gmail.com
Same issue here. How can i fix this bug?
ch...@google.com
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
la...@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.
am...@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
la...@google.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!!
am...@gmail.com
am...@gmail.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.
la...@google.com
Just would like to add that we are experiencing this on device as well, not just in AVD. Not sure if that matters...
am...@gmail.com
Any ETA on this fix? Appreciate your reply.
la...@google.com
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.
am...@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.
la...@google.com
I agree, please update the documentation while it is not working.
am...@gmail.com
Agreed on updating the documentation. I wasted two days on this issue and it pains me to see it repeated Ad nauseam.
am...@gmail.com
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.
la...@google.com
This should go out today.
am...@gmail.com
@howardb Thank Jah!
am...@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?
am...@gmail.com
Sorry, we're only committing to keeping the latest API up-to-date.
am...@gmail.com
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
am...@gmail.com
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...
am...@gmail.com
After updating my sdk to API 18, my AVD doesn't play any sound.
am...@gmail.com
2.3
Instant Run OFF
Log OFF
19.8s
2.3
Instant Run ON
Log OFF
20.1s
Instant Run OFF
Log OFF
19.8s
2.3
Instant Run ON
Log OFF
20.1s
am...@gmail.com
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?
la...@google.com
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.
Description
supply all required information.
Studio Build: 2.2 rc2
OS: Win 10
Steps to Reproduce:
When attaching the debugger the app will now hang. AS will spool through roughly hundreds of "loaded module [module]" messages. It will finally attach, but this process takes at least 20 seconds. Previously I could attach in moments. This happens on every attach so it's a decent burden on debugging.
Perhaps this is a new configuration I'm lacking, but I couldn't find anything in the notes.