Fixed
Status Update
Comments
xa...@google.com <xa...@google.com>
jo...@google.com <jo...@google.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
jo...@google.com <jo...@google.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"
mi...@gmail.com <mi...@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
ch...@google.com <ch...@google.com>
jo...@google.com <jo...@google.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
mi...@gmail.com <mi...@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
jo...@google.com <jo...@google.com> #7
same
jo...@google.com <jo...@google.com> #8
SAME ! - Google can't do sth working in 100 percent?
jo...@google.com <jo...@google.com> #9
same issue - Google Play services out of date. Requires 3159100 but found 3158130
jo...@google.com <jo...@google.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
mi...@gmail.com <mi...@gmail.com> #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
jo...@google.com <jo...@google.com> #12
Same issue here.
jo...@google.com <jo...@google.com> #13
Same issue here. How can i fix this bug?
jo...@google.com <jo...@google.com> #14
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
da...@google.com <da...@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.
mi...@gmail.com <mi...@gmail.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
jo...@google.com <jo...@google.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!!
da...@google.com <da...@google.com> #18
jo...@google.com <jo...@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.
ch...@google.com <ch...@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...
jo...@google.com <jo...@google.com> #21
Any ETA on this fix? Appreciate your reply.
mi...@gmail.com <mi...@gmail.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
The exported JSON is missing more than half of the source files indicated in my
our project actually has
eg:
include Android_proj_A.mk
include Android_proj_B.mk
...
The end result of all this is that several of our .so files are not built, curiously this does not trigger any kind of build failure, and the .apk is built and deployed, without the required .so files. Our app then crashes spectacularly the moment we attempt to load the native library via System.loadLibrary() in Java due to the lack of said .so files in the apk.
Steps To Reproduce:
Unfortunately I don't have a sample project to provide at this time however the steps to reproduce are fairly straightforward:
1) create a project that uses a Gradle configuration to build with ndkBuild
2) possibly use the reference structure mentioned above in the .mk files
3) perform a gradle sync using gradle 2.3.0Beta2 and Gradle Wrapper 3.3
4) compare the output JSON from the last successful one, in my case it was less than half the size and missing all kinds of information.
5) edit gradle-wrapper.properties to roll back to 2.14.1 and edit build.gradle to roll back to 2.2.3
6) Sync again, the JSON is generated correctly.
Expected Results:
JSON is generated with exact same contents in either case.
Version Information:
Android Studio 2.3 Beta 2
Build #AI-162.3616766, built on January 6, 2017
JRE: 1.8.0_112-release-b06 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10
Gradle Version: 2.3.0-beta2
Android Plugin Version: 3.3
Android SDK tools Versioni 25.2.5
Compile SDK Version: API 23
Build Tools Version: 25.0.2
let me know if I can provide any additional information that may be of assistance.