New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 797080 link

Starred by 24 users

Issue metadata

Status: Fixed
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Can't turn mic on Chrome V64 due to policy change

Reported by adefa...@gmail.com, Dec 21 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.24 Safari/537.36

Steps to reproduce the problem:
1. Attempt to place a call using hangouts extension

What is the expected behavior?
Call is placed.

What went wrong?
Call is not placed. Instead a Hangouts says it needs permission to use the mic and a window is opened. There is nothing in the window, nothing to push to grant hangouts permission.

I use the Hangouts extension to make and receive calls. Suddening I can't make phone calls. Specifically I get "Hangouts needs access to your microphone to make calls. See the popup window to resolve this issue". Looking at the errors I see "AudioCapture permission has been blocked because of a Feature Policy applied to the current document - See https://goo.gl/EuHzyv for more details". That web link is https://sites.google.com/a/chromium.org/dev/Home/chromium-security/deprecating-permissions-in-cross-origin-iframes.

Note that Hangouts does popup a window but the window is blank/empty. Viewing source I see:

<!DOCTYPE html><html><head><title>Hangouts</title><link type="text/css" rel="stylesheet" href="/_/scs/talk-static/_/ss/k=wcs.webrtcpermission.1u9nl6q3fo7f.L.W.O/m=webrtcpermission/am=AoAg/d=1/rs=AGyH-FtFHVBRms0fBELPRDu_3SF9tM57AQ"></head><body><script id="base-js" type="text/javascript" src="/_/scs/talk-static/_/js/k=wcs.webrtcpermission.en.l9uvKb_Os0Q.O/m=webrtcpermission/am=AoAg/rt=j/d=1/rs=AGyH-FudfDevUYx4YmjkolTxGZ2VGWVA9g"></script></body></html>

Yes that's a web page with only a <script> tag in the body. No button to push.

I can keep a web page up at https://hangouts.google.com but it was easier to use the extension and not miss calls.

How can I fix this?

Did this work before? Yes Previous version before V64 rolled out. Sorry didn't capture previous version number

Chrome version: 64.0.3282.24  Channel: beta
OS Version: Ubuntu 16.10
Flash Version: N/A

https://hangouts.google.com is a workaround but it's UI bites!
 
Labels: Needs-Triage-M64
Cc: abdulsyed@chromium.org manoranj...@chromium.org
Labels: Needs-Bisect
Cc: sc00335...@techmahindra.com
Labels: Triaged-ET TE-NeedsTriageFromHYD
adefaria@ Thanks for the issue.

Tested this issue on Ubuntu 14.04, 17.10 and Mac OS 10.12.6 using the latest Stable 63.0.3239.132 and reported version 64.0.3282.24 and unable to reproduce the issue by following the below steps.

1. Launched Chrome and added Hangouts extension.
2. Placed a Hangout call and a popup was shown asking to allow/block the Microphone and Camera.
3. On allowing, the Hangouts call was placed without an issue.
Attached is the screen shot for reference.

As the issue was reported on Ubuntu 16.10, requesting someone from Inhouse team to please look into this issue and help in further triaging.

Thanks..

797080.png
20.4 KB View Download

Comment 5 by adefa...@gmail.com, Jan 5 2018

From the screenshot you seem to have done a video call, not just a regular call. I have very few people I can video call. Can you try to reproduce will just a straight phone call and/or maybe an incoming call? Might need to remove mic permission first.

I tried a video call and it seemed to be working although I didn't really want to call that person. The larger screen came up and it say calling <name>; it showed my video cam and did not really ask about the michrophone. However I quickly hung up as I didn't want to actually call this person (it's too early in the morning right now).

As my main usage of Hangouts is placing and importantly receiving regular phone calls (currently unemployed and need to talk to recruiters) this is important to me.

Thanks.
Labels: -Needs-Bisect M-64
Owner: efernandez@google.com
Status: Assigned (was: Unconfirmed)
efernandez@ is looking into it.
We're experiencing the same call-only issue when using Chrome V64 Beta.
2018-01-08 at 13-24-20.png
6.5 KB View Download
This issue has affected our Windows 10 pc's for more than two months, both dev and canary channels.

It is possible to make calls through https://hangouts.google.com (the blocked media icon appears) but not through https://mail.google.com.  At mail.google.com (gmail), no blocked media icon appears, the message on the blue background reads "Hangouts needs access to your microphone to make calls. Click the blocked media icon at the top of your browser", and Dev Tools Console continually prints the error:

  AudioCapture permission has been blocked because of a Feature Policy applied to the current document. See https://goo.gl/EuHzyv for more details.    /mail/u/0/#inbox:1

Strangely, Gmail is able to place a call provided that a microphone is NOT connected to the Windows pc -  pointless unless one communicates by dial pad touch tone, but strange nonetheless.

The issue is not related to extensions or profile settings. It affects the guest profile and new profiles in both dev and canary on multiple pc's.

Currently we have the following but the issue predates these versions:

  Google Chrome	65.0.3315.3 (Official Build) dev (64-bit) (cohort: Dev)
  Revision	e3b7a8643b5a46f3483a85bb20d25213b84a8906-refs/branch-heads/3315@{#4}

  Google Chrome	65.0.3318.0 (Official Build) canary (64-bit) (cohort: Clang-64)
  Revision	193c7425ab494d87b07d70a1df512d58fcd58b58-refs/heads/master@{#528541}

  Microsoft Windows Version 1709 (OS Build 16299.192)


The issue does not affect Linux and Mac OS Chrome 63.  Chrome 63 on MacOS reports the following in Dev Tools Console:

  [Deprecation] getUserMedia (microphone) usage in cross-origin iframes is deprecated and will be disabled in M64, around January 2018. To continue to use this feature, it must be enabled by the embedding document using Feature Policy, e.g. <iframe allow="microphone" ...>. See https://goo.gl/EuHzyv for more details.

Does this mean that hangouts calls through gmail will soon stop working on chrome stable across all platforms?
Status: Fixed (was: Assigned)
This is now fixed on Gmail.
I can confirm that it works.  Thanks for fixing this.

Google Chrome 65.0.3323.0 (Official Build) canary (64-bit) (cohort: Clang-64)
Revision 470d3a6be2f380affa8de3dc0dd1508f3eeba9f7-refs/heads/master@{#529554}
OS Windows

Comment 12 by adefa...@gmail.com, Jan 18 2018

I'm not sure what "fixed on Gmail" means, I reported this against the extension. It still doesn't work as an extension nor does it work from gmail.
It didn't work for me in gmail until I restarted Chrome canary.  I think the change was just pushed out.  
Status: Started (was: Fixed)
Right about the extension. We'll need to push a new version with the fix, I'll mark fixed once that's done.

Comment 15 by adefa...@gmail.com, Jan 18 2018

Excuse me, I'm kinda new to this. I'm using Google Chrome Beta version yet people speak of Canary. I assume the fix will go in Canary first. When might I see it in Beta?
If the Fix is applied to the Extension (which is what it sounds like in Comment #14) it will go out to everyone, not just Canary.
This is now affecting the Stable Channel, and the attempted fix to "allow='microphone'" did not solve the issue.
efernandez@ what is the exact issue, and what is the fix? Is it already in canary? Is this only affecting Linux? 

Comment 19 by adefa...@gmail.com, Jan 24 2018

The exact issue is that that Hangout's extension prompts to allow use of the mic but the prompt is not seen (window is blank) and the use cannot allow usage of the mic. This stops both incoming and outgoing calls through the Hangouts extension. I know it effects me on Ubuntu. Don't know if it's fixed in canary as I don't run canary.
The fix was to go out to the Extension (not to the Browser).  This is affecting Linux, Windows, Mac, and Chromebooks.


I've locally modified the Chrome extension and verified it works. I just added b.allow="microphone"; to line 160 of the host.js file of the extension, immediately before the e.appendChild(b); on that line. I've also attached the modified file for reference.

This temporary fix is useful if you need to be able to make and receive voice calls on Chrome 64+ while waiting for the official update to the extension.
host.js
67.6 KB View Download

Comment 22 by adefa...@gmail.com, Jan 25 2018

You know there'd be a lot less postings, emails, discussion, etc. if simple things like this were just fixed and release. I doubt it would take more than a few minutes to do.

Chrisi... I'm sure there is some method of modifying the extension locally but I don't know what that method is. IOW why not attach the full extension?
I've attached the full extension with the modified file. The zip file only saves a couple steps, but it is slightly easier to use.

I wasn't sure if attaching the full extension would be acceptable, as installing extensions from an untrusted source (such as from a semi-random user here) isn't best practice. Since there's no trust, you don't know if malicious code has been added unless you're skilled enough to verify the code, in which case my previous instructions would be sufficient anyway.

Also, the official extension will hopefully be updated in short order, in which case users should know to uninstall this temporary version in favor of the official version.

So, I think there are plenty of reasons for me not to attach the zipped version, but here it is anyway. I recommend against installing this version because it goes against best practice, but I also recognize that not having a working extension makes it very difficult to work in Hangouts if you require voice capability.
Hangouts.zip
639 KB Download

Comment 24 by adefa...@gmail.com, Jan 25 2018

Thanks! I can verify that it works too!

I assume when the real extension is uploaded and available it'll replace this no? If I need to do something to get on board with the official extension let me know.
You'll need to uninstall this version, as this is treated as a different extension than the official version. You should see a popup every time you start Chrome indicating that some developer mode extensions are running, which hopefully will be annoying enough to uninstall this version as soon as the official version is updated. :)

Comment 26 by adefa...@gmail.com, Jan 25 2018

Thanks again. I'll have to remember that as I typically never restart chrome. I have it running for weeks or months if I can...
Thanks for the modified Hangouts extension. Just letting everyone know there was a separate thread for this issue dating back Sep 2016 https://bugs.chromium.org/p/chromium/issues/detail?id=646601

There's currently a Hangouts product forum discussion as well: https://productforums.google.com/forum/?#!msg/hangouts/qrQ_IHVHdRE/uWRfyLzNAwAJ
anyone tell me how to install the modified hangouts extension?

Comment 29 by adefa...@gmail.com, Jan 29 2018

Get the updated Hangouts.zip, unzip it, then go to extensions in Chrome and click on Load unpacked extension.

Comment 30 by da...@zemon.name, Jan 29 2018

Important to note that "Load unpacked extension" only works if you enable developer mode at the top of the page first.

However, despite that, sound still didn't work for me. I was able to place calls without the blank popup window getting in the way, but the user on the other end could not hear me.
Yaaaa! Thanks! I can verify that the zipped file attached to this page 
fixed the funky-ass blank window issue for me on Chrome on Linux!!

-db

Comment 32 by adefa...@gmail.com, Jan 30 2018

Looks like the fixed version has been pushed out to the webstore and it seems to work so we can mark this fixed.
Status: Fixed (was: Started)
I can dial out now however the other party can't hear me. I tested my headset with mic on other platforms and they all work. 
Also forgot to add that I haven't gotten any phone or text notifications from the hangout app however they are showing in my gmail inbox as being received.
Cc: susanjun...@techmahindra.com efernandez@google.com
 Issue 807718  has been merged into this issue.

Comment 37 by gcl...@gmail.com, Feb 20 2018

I am facing the mic permission issue after the v64 update but from using the mic from iframe. allow=microphone fix recommended is also not helping. is there any fix available for this issue. 

getting this error message in console log.

AudioCapture permission has been blocked because of a Feature Policy applied to the current document. See https://goo.gl/EuHzyv for more details.

Comment 38 by adefa...@gmail.com, Feb 20 2018

This has been fixed already in the Hangouts extension version 2018.123.418.2.

Comment 39 by gcl...@gmail.com, Feb 20 2018

what about issue accessing mic from iframe for regular web applications. ??

Comment 40 by adefa...@gmail.com, Feb 20 2018

What "regular web applications"? Do you mean https://hangouts.google.com? If so that was working for me but has a poor UI. Besides this bug was submitted by me and was only really about the extension itself.

Comment 41 by gcl...@gmail.com, Feb 20 2018

"regular web application" mean the application that are custom build and we are using google cloud speech api in our web application and it opens in iframe. Mic feature stopped working after v64 update due to "Audio capture permission blocked" issue.

Comment 42 by adefa...@gmail.com, Feb 20 2018

I think you should open up a case about that separately.

Comment 43 by gcl...@gmail.com, Feb 20 2018

root cause of both the issue are same and i dont see need to open new case. but i am opening as per your request. 

this below case is for browser based application has mic and rendering in iframe.

https://bugs.chromium.org/p/chromium/issues/detail?id=813858
I am seeing this problem with Hangouts extensions 2018.515.419.1 on Chrome 71.0.3572.0
Yeah me too. Not good.
This issue just started today for me. Chrome updated to version 71.0.3578.80 (Official Build) (64-bit) last night. I'm on Windows 10 version 1809 build 17763.134.

Have tried all fixes to no avail. Tried reinstalling the Chrome extension, tried installing the OLD Chrome "app", nothing works.

The Hangouts extension worked perfectly for me until today.
"This issue just started today for me. Chrome updated to version 71.0.3578.80 (Official Build) (64-bit) last night. I'm on Windows 10 version 1809 build 17763.134.

Have tried all fixes to no avail. Tried reinstalling the Chrome extension, tried installing the OLD Chrome "app", nothing works.

The Hangouts extension worked perfectly for me until today."

Me too.
Is this issue marked "Fixed" because there was an underlying problem with the Chrome browser, or is this thread/issue specifically for the Hangouts extension?

If Chrome was "fixed" then the Hangouts extension needs an update.

If the Hangouts extension was "fixed" then it needs another fix or there's a bug in Chrome.

If four people have responded that there is an issue with Chrome 71 + the Hangouts extension, the problem must rest with one or the other... When can we expect a fix? I use the Hangouts extension 24/7 (always open on another monitor).

Many thanks!
this issue not fixed on my end.

chrome:
Version 71.0.3578.80 (Official Build) (64-bit)

Hangout extension:
2018.1108.1646.1

linux mint mate 17 Qiana
(Ubuntu 14.04.3 LTS)

I also I'm having this problem just noticed it today. You would think but this would have been fixed a long time ago. I know that Hangouts is kind of going away but I would really like to have this fixed because I use it quite often.
So any help would be appreciated thank you. 
I am also having the described issue of not being able to make any calls in the Hangouts extension. I am on Chrome 71.0.3578.80 in Windows 10 1803. 

The extension has worked fine for months, dare  I say even years, and just recently started this behavior. 

When I try making a call using the extension, I receive an error "Hangouts needs access to your microphone to make calls. Click the allow button at the top of your browser." However, there is nothing to click to allow within the extension. If I try on hangouts.google.com with the extension enabled, I will experience the same behavior. However, if I disable the hangouts extension and use hangouts.google.com, it will work. 

Attached is a cropped screenshot for reference. 
hangouterror.png
12.2 KB View Download
Forgot  to mention I have Hangouts Extension 2018.1108.1646.1_0 in Comment 51.
Same issue here.
Chrome 71.0.3578.80 
Hangounts extension 2018.1108.1646.1


After trying several fixes I got the blue popup to show but it doesn't show the permission so it's useless.
If I use the Chrome app it works but that only works when I want to make calls, if someone calls me it doesn't work unless the app is running full time.


It's considered "fixed" because the writing is on the wall for Hangouts, my friends. For the time being you can use hangouts.google.com to make and receive calls. The extension is kaput until we get migrated over to Hangouts Meet for voice and video calls. I went back to using the GVoice app and website separately now. May as well get used to it now.
Hangouts days might be numbered but I had heard of Google making some sort of "Consumer version" of Hangouts along with the G-Suite version of Hangouts. Might I be so bold to think that perhaps I might in some day in the future be using a "consumer version" of Hangouts and quite frankly I'd really like to have the mic work. I'm strange like that. And it's not a stretch to think that developers will hall this version of Hangouts source code to be the basis of this consumer version. Why not fix the problem and then haul the code with the fixes along with it?
The update for Chrome today (Version 71.0.3578.98) (64-bit) did not fix this.
Confirmed in 71.0.3578.98 - NOT FIXED.  

The only way to get hangouts.google.com to work is to DISABLE the Hangouts Extension in Chrome.
Hangouts 2018.1108.1646.1 and chrome Version 71.0.3578.98 (Official Build) (64-bit) not working.  I get a little popup window when I try making a call but it is blank and no mic prompt.
That's strange because those exact same version numbers just started working for me! It's great to have it back. Killed two pinned tabs I was keeping (Voice and Hangouts).

jwfaer, maybe a reinstall?
I spoke too soon! While I do have the Hangouts extension working and it handles texts it does not handle phone calls - at least not outgoing calls. Making a call does not hook up with the audio systems at all so I cannot hear nor talk on the call. I had to turn off the extension to use hangouts.google.com to actually make calls. Ugh!
I have been chasing this problem for months now.  This is chrome beta (72.0.3626.17) on MacOS (10.14.2) with hangout extension.   I just updated to latest hangout extension (2018.1213.1433.1) with the hope that this issue may be resolved.  I still get the "hangout needs permission" window with no options to click anywhere to allow.  
The latest version of the Hangouts extension (2018.1213.1433.1) seems to have corrected this issue.

Thank you, magical bugfixing fairies!
Define "corrected this issue". Sure it doesn't get stuck with a blank page but it doesn't work either. I get no connection to audio from Hangouts extension. Can't hear callers, can't talk to them. Yes I have that Hangouts extension version. What version of the browser do you have?
On Windows 10, with the latest Chrome release version 71.0.3578.98 (Official Build) (64-bit) AND the latest Hangouts extension release version 2018.1213.1433.1, my system is working as it had before. It asked for microphone permission, popped up a window, but it wasn't blank this time, and I was able to "Allow" mic access. I tested calling a friend and it worked perfectly.

If you setup is identical to mine, try reinstalling the extension is all I can suggest.
I'd first need to install Windows 10. That ain't gonna be happening. Plus I'm on Chrome Beta (72.0.3626.17). I suspect that this broke again because of that. People who fix these things should keep the future versions in mind but I guess they aren't...

Sign in to add a comment