Feature Request P2
Status Update
Comments
to...@chromium.org <to...@chromium.org> #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
ya...@chromium.org <ya...@chromium.org> #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"
to...@chromium.org <to...@chromium.org> #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
[Deleted User] <[Deleted User]> #5
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
pf...@chromium.org <pf...@chromium.org> #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
[Deleted User] <[Deleted User]> #7
same
to...@chromium.org <to...@chromium.org> #8
SAME ! - Google can't do sth working in 100 percent?
bm...@chromium.org <bm...@chromium.org> #9
same issue - Google Play services out of date. Requires 3159100 but found 3158130
is...@google.com <is...@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
to...@chromium.org <to...@chromium.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
ch...@google.com <ch...@google.com> #12
Same issue here.
to...@chromium.org <to...@chromium.org> #13
Same issue here. How can i fix this bug?
ch...@google.com <ch...@google.com> #14
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
Description