Fixed
Status Update
Comments
sa...@chromium.org <sa...@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
sa...@chromium.org <sa...@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"
gu...@google.com <gu...@google.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
ca...@vidyard.com <ca...@vidyard.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
[Deleted User] <[Deleted User]> #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
gu...@chromium.org <gu...@chromium.org> #8
SAME ! - Google can't do sth working in 100 percent?
gu...@chromium.org <gu...@chromium.org> #9
same issue - Google Play services out of date. Requires 3159100 but found 3158130
bu...@chops-service-accounts.iam.gserviceaccount.com <bu...@chops-service-accounts.iam.gserviceaccount.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
gu...@chromium.org <gu...@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
gu...@chromium.org <gu...@chromium.org> #12
Same issue here.
gu...@chromium.org <gu...@chromium.org> #13
Same issue here. How can i fix this bug?
ma...@chromium.org <ma...@chromium.org> #14
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
sh...@chromium.org <sh...@chromium.org> #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.
go...@chromium.org <go...@chromium.org> #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
bu...@chops-service-accounts.iam.gserviceaccount.com <bu...@chops-service-accounts.iam.gserviceaccount.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!!
gu...@chromium.org <gu...@chromium.org> #18
gu...@chromium.org <gu...@chromium.org> #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.
ma...@chromium.org <ma...@chromium.org> #20
Just would like to add that we are experiencing this on device as well, not just in AVD. Not sure if that matters...
sr...@google.com <sr...@google.com> #21
Any ETA on this fix? Appreciate your reply.
gu...@chromium.org <gu...@chromium.org> #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.
gu...@chromium.org <gu...@chromium.org> #23
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.
gu...@chromium.org <gu...@chromium.org> #24
I agree, please update the documentation while it is not working.
rs...@chromium.org <rs...@chromium.org> #25
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 <is...@google.com> #26
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.
pe...@google.com <pe...@google.com> #27
This should go out today.
Description
Steps to reproduce the problem:
1. Make sure new Catalina screen sharing permissions are enabled for chrome
2. Make Chrome fullscreen
3. go to
3. Click Share your screen and select your entire screen -> "NotAllowedError: Permission denied by system"
To make it work:
4. Refresh and click share your screen again
5. With the screen select prompt open bring your mouse up to the top of the screen to expand the title bar and then select to share your entire screen
6. Permissions should correctly allow you to share your screen.
What is the expected behavior?
What went wrong?
screen sharing fails when chrome is fullscreen and title bars are not expanded in Catalina
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: 80.0.3963.0 Channel: canary
OS Version: OS X 10.15.1
Flash Version:
Confirmed this in a few video recording chrome extensions
seems related to but I dont see any mention of fullscreen: