Status Update
No update yet.
Comments
jh...@chromium.org
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
ph...@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"
ph...@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
ja...@chromium.org
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
an...@visiquate.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
an...@visiquate.com
same
re...@chromium.org
SAME ! - Google can't do sth working in 100 percent?
an...@visiquate.com
same issue - Google Play services out of date. Requires 3159100 but found 3158130
od...@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
an...@visiquate.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
od...@chromium.org
Same issue here. How can i fix this bug?
an...@visiquate.com
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
an...@visiquate.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.
od...@chromium.org
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
od...@chromium.org
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!!
ma...@google.com
an...@visiquate.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.
[Deleted User] <[Deleted User]>
Just would like to add that we are experiencing this on device as well, not just in AVD. Not sure if that matters...
re...@chromium.org
Any ETA on this fix? Appreciate your reply.
re...@chromium.org
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.
cm...@chromium.org
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.
cm...@chromium.org
I agree, please update the documentation while it is not working.
ch...@google.com
Agreed on updating the documentation. I wasted two days on this issue and it pains me to see it repeated Ad nauseam.
is...@google.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.
Description
Steps to reproduce the problem:
1. Pair BLE device(ex. blood glucose measuring device) which has over 100 values stored
2. Log what is served via characteristicvaluechanged event
3. Inspect console(i have placed incremented variable just to see count)
(proper command was used to write in to characteristic with access permission WRITE to trigger characteristicvaluechanged event of characteristic with permission NOTIFY, and listener was placed to this characteristic with NOTIFY permission)
What is the expected behavior?
Device should return all stored values.
What went wrong?
On windows using chrome device is returning all stored values,
on macOS chrome is returning near 70%(not always same amount) of all values stored on device. Wasn't able to see anything useful on macOS console.
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: 80.0.3987.122 Channel: stable
OS Version: OS X 10.15.2
Flash Version:
I am not able to test it on other similar devices, there is chance it is device related, but because it works well on Windows it might be OS related.