Closed Bug 1928216 Opened 1 year ago Closed 7 months ago

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

Categories

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

Product:
Web Compatibility
Component:
Site Reports
Version:
Firefox 132
Platform:
Desktop
All
Type:
defect

Tracking

(Webcompat Priority:P3, Webcompat Score:4, firefox-esr115 unaffected, firefox-esr128 unaffected, firefox130 unaffected, firefox131 disabled, firefox132+ wontfix, firefox133+ verified, firefox134+ verified)

Status:
RESOLVED WORKSFORME
Project Flags:
Webcompat Priority P3
Webcompat Score 4
Tracking Flags:
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- unaffected
firefox130 --- unaffected
firefox131 --- disabled
firefox132 + wontfix
firefox133 + verified
firefox134 + verified

People

(Reporter: keven, Assigned: jib)

References

(Regression,
URL
)

Details

(4 keywords, Whiteboard: [qa-triaged])

User Story

platform:windows,mac,linux,android
impact:workflow-broken
configuration:common
affects:all
branch:release
user-impact-score:80
diagnosis-team:video-conferencing

Attachments

(4 files)

20241031-Regession_Info.txt
165.92 KB, text/plain
Details
Bug 1928216 - webcompat intervention for Google Voice not handling permissions.query() working for cam/mic. r?twisniewski
48 bytes, text/x-phabricator-request
Details | Review
Bug 1928216 - webcompat intervention for Google Voice not handling permissions.query() working for cam/mic
48 bytes, text/x-phabricator-request
phab-bot
: approval-mozilla-beta+
Details | Review
Bug 1928216 - remove our JS webcompat intervention for Google Voice; r?denschub
48 bytes, text/x-phabricator-request
Details | Review

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.

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

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/

Flags: needinfo?(keven)

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.

Flags: needinfo?(keven)

Full log file from moz-regression.

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.

Flags: needinfo?(keven)

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

Flags: needinfo?(keven)

(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.

Status: UNCONFIRMED → NEW
status-firefox130: --- → unaffected
status-firefox131: --- → disabled
status-firefox132: --- → affected
status-firefox133: --- → affected
status-firefox134: --- → affected
status-firefox-esr115: --- → unaffected
status-firefox-esr128: --- → unaffected
Ever confirmed: true
Keywords: regression
Regressed by: 1609427, 1916993

Any thoughts on this, Jan-Ivar?

Flags: needinfo?(jib)
Component: Untriaged → WebRTC: Audio/Video
Product: Firefox → Core

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.

Severity: -- → S2
Flags: needinfo?(jib)
OS: Unspecified → All
Priority: -- → P1
No longer regressed by: 1916993
Hardware: Unspecified → Desktop
Summary: Version 132 does not detect my microphone while 131 still works. → Google Voice doesn't list microphones in Firefox 132 while it still works in 131

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.

Flags: needinfo?(jmathies)

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

Flags: needinfo?(jib)
Assignee: nobody → jib
Status: NEW → ASSIGNED

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

status-firefox132: affected → wontfix
Attachment #9436251 - Flags: approval-mozilla-beta?
Pushed by twisniewski@mozilla.com: 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

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

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox134: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → 134 Branch

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
Flags: qe-verify+
Flags: needinfo?(jmathies)
Flags: needinfo?(jib)
Attachment #9436251 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
Component: WebRTC: Audio/Video → Site Reports
Product: Core → Web Compatibility
Target Milestone: 134 Branch → ---
Whiteboard: [qa-triaged]

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

Status: RESOLVED → VERIFIED
status-firefox133: fixed → verified
status-firefox134: fixed → verified
Flags: qe-verify+
Duplicate of this bug: 1932846

Pardon the spam, but I'm reopening this bug, as we're now tracking the status of webcompat issues with interventions differently (keeping them open until the underlying issue is actually fixed).

Status: VERIFIED → REOPENED
Keywords: webcompat:contact-ready, webcompat:sitepatch-applied
Resolution: FIXED → ---
URL: https://voice.google.com
User Story: (updated)
Webcompat Priority: --- → P1
Webcompat Score: --- → 8
Keywords: webcompat:site-report
Webcompat Score: 8 → 4

Google submitted a fix in December so this intervention is no longer needed. Thanks!

I've confirmed this by disabling the "voice.google.com" intervention in about:compat and clicking the 🎧 icon in Voice to list available microphones (after a permission prompt).

Flags: needinfo?(twisniewski)

This is broken again for me on 137.0.2. The workaround of using about:compat doesn't fix it either. See https://support.google.com/voice/thread/339314765/google-voice-wont-use-my-mic?msgid=340682072

(In reply to T Miller from comment #23)

This is broken again for me on 137.0.2. The workaround of using about:compat doesn't fix it either. See https://support.google.com/voice/thread/339314765/google-voice-wont-use-my-mic?msgid=340682072

Looks like web based Google voice is broken on Chrome 135.0.7049.96 on Windows 10 too.

The older interface still works in Firefox with this URL: https://www.google.com/voice/redirection/voice#phones

User Story: (updated)
Webcompat Priority: P1 → P3

(In reply to T Miller from comment #23)

This is broken again for me on 137.0.2. The workaround of using about:compat doesn't fix it either. See https://support.google.com/voice/thread/339314765/google-voice-wont-use-my-mic?msgid=340682072

Hi Troy, that link isn't working for me. Can you summarize?

I'm not able to reproduce, but I also get the same old UI from both https://voice.google.com/u/0/calls and the URL in comment 25.

Are you part of an A/B test perchance? Can you upload a screenshot of the problem in the new UI (removing any personal info of course)?

If the UI has changed, we'll reach out to see what's up.

Flags: needinfo?(troy.d.miller)

Appears that support.google.com thread was deleted and I can't access either even though I posted to the thread. Sad.

I am now on Firefox 138.0.1 and the latest forced refresh of this voice now has a working mic.

I'm sorry I didn't capture a screenshot of when it failed. I'll try to remember to that if it fails again.

Flags: needinfo?(troy.d.miller)

Glad to hear it is working again. Closing based on comment 22. Please reopen if it breaks again.

Status: REOPENED → RESOLVED
Closed: 1 year ago → 7 months ago
Resolution: --- → FIXED
Pushed by twisniewski@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0def1c551c4b remove our JS webcompat intervention for Google Voice; r=denschub,webcompat-reviewers
Flags: needinfo?(twisniewski)
Resolution: FIXED → WORKSFORME

A patch has been attached on this bug, which was already closed. Filing a separate bug will ensure better tracking. If this was not by mistake and further action is needed, please alert the appropriate party. (Or: if the patch doesn't change behavior -- e.g. landing a test case, or fixing a typo -- then feel free to disregard this message)

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: