1928216 - Google Voice doesn't list microphones in Firefox 132 while it still works in 131

Status: VERIFIED FIXED

(Web Compatibility :: Site Reports, defect, P1)

Description

[Keven Webb]

Steps to reproduce:

Windows 10 Pro. Upgraded from 131 to 132. Went to voice.google.com. Clicked on Microphones icon.

Actual results:

No microphones were detected.

Expected results:

After installing 131.0b9, the microphones were detected.
** I am currently running this older version.

Comment 1

[Keven Webb]

My user agent info is not valid since I submitted from another browser.

Comment 2

[Ryan VanderMeulen [:RyanVM]]

Hi Keven, thanks for the report. Any chance you could try to help narrow down when this broke using the mozregression tool? It'll help us get this report in front of the right people much faster. Thanks!
https://mozilla.github.io/mozregression/

Comment 3

[Keven Webb]

Here is the final result:

2024-10-31T10:28:40.933000: DEBUG : Found commit message:
Bug 1609427 - Don't report Always Ask as "granted" if the privacy.resistFingerprinting pref is set. r=pbz

Differential Revision: https://phabricator.services.mozilla.com/D217644

2024-10-31T10:28:40.933000: DEBUG : Did not find a branch, checking all integration branches
2024-10-31T10:28:40.933000: INFO : The bisection is done.
2024-10-31T10:28:40.935000: INFO : Stopped

Also attaching the full log file.

Comment 4

[Keven Webb]

Attachment: 20241031-Regession_Info.txt

Full log file from moz-regression.

Comment 5

[Ryan VanderMeulen [:RyanVM]]

Does it work if you set the permissions.media.query.enabled pref to false in about:config? That pref was added by the bug that mozregression bisected to and the pref was set to true by default for 132+ in bug 1916993. So that would at least fit your observations.

EDIT: You might also need to set media.devices.enumerate.legacy.enabled to true.

Comment 6

[Keven Webb]

Setting permissions.media.query.enabled to **false **worked. I did not have to reset media.devices.enumerate.legacy.enabled.

Comment 7

[Keven Webb]

(In reply to Keven Webb from comment #6)

Setting permissions.media.query.enabled to false worked. I did not have to reset media.devices.enumerate.legacy.enabled.

Comment 8

[Ryan VanderMeulen [:RyanVM]]

Any thoughts on this, Jan-Ivar?

Comment 9

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

Thanks Keven! Can you confirm that calls still work for you?

I'm able to reproduce (macOS). The bug seems confined to Google Voice's microphone picker UI being blank. Calls still WFM.

• I'm still able to make calls using my default microphone, and others can hear me.
• (at least on macOS) I also confirmed it works to put on my airPods and make a call with them.

Workarounds

• Ignore the picker and make calls as usual (should work for most folks with limited number of microphones)
• Taking airpods out of their case or putting them back in their case while Google Voice is open fixes the bug (the UI refreshes to show the correct microphone list)
• Turning off/on any bluetooth device or toggling bluetooth off/on in the OS should work as well.
• Basically, any action that triggers a devicechange event appears to cause Google Voice to refresh its picker correctly.

A more permanent workaround is to set permissions.media.query.enabled to false in about:config

Cause

The symptom appears provoked by permissions.query({name: "microphone"}) working in 132 whereas in 131 it rejects. Why this would cause Google Voice problems seems unclear, but if browser sniffing is involved (common around device handling), it might be triggering an untested code-path in their app.

I see no obvious Firefox bug here. I will reach out to Google immediately to see if this can be fixed on their end.

Comment 10

[BugBot [:suhaib / :marco/ :calixte]]

The bug is marked as tracked for firefox132 (release), tracked for firefox133 (beta) and tracked for firefox134 (nightly). However, the bug still isn't assigned.

:jimm, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Comment 11

[Ryan VanderMeulen [:RyanVM]]

Is it possible we could create a webcompat intervention for this otherwise while we wait for Google to address it on their end?

Comment 12

[Jan-Ivar Bruaroey [:jib] (needinfo? me)]

Attachment: Bug 1928216 - webcompat intervention for Google Voice not handling permissions.query() working for cam/mic. r?twisniewski

Comment 13

[Ryan VanderMeulen [:RyanVM]]

Per Slack, we're going to target v133 for this intervention rather than rushing it into a v132 dot release with minimal testing.

Comment 14

[Thomas Wisniewski [:twisniewski]]

Attachment: Bug 1928216 - webcompat intervention for Google Voice not handling permissions.query() working for cam/mic

Comment 15

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/9b7bf727a8b3
webcompat intervention for Google Voice not handling permissions.query() working for cam/mic. r=twisniewski,webcompat-reviewers

Comment 16

[Norisz Fay [:noriszfay]]

https://hg.mozilla.org/mozilla-central/rev/9b7bf727a8b3

Comment 17

[Phabricator Automation]

beta Uplift Approval Request

• User impact if declined: Google Voice will not list microphones.
• Code covered by automated testing: no
• Fix verified in Nightly: no
• Needs manual QE test: yes
• Steps to reproduce for manual QE testing: Login to voice.google.com, click on the Microphones icon, and confirm that microphones are listed.
• Risk associated with taking this patch: Low
• Explanation of risk level: Only affects our webcompat addon and Google Voice, which is broken without this fix, so things can't get much worse.
• String changes made/needed: no
• Is Android affected?: no

Comment 18

[Pulsebot]

https://hg.mozilla.org/releases/mozilla-beta/rev/7bc7ca280e14

Comment 19

[Peter Magyari (Desktop QA)]

Verified fixed on Nightly 134.0a1 (20241111094531) and Beta 133.0b7 (20241111092015).