1490154 - In WebEx, could not acquire local media.

Status: NEW

(Core :: WebRTC, defect, P3)

Description

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

STR:
 1. Open https://teams.webex.com/ and log in with an account
 2. Click the 📞
 3. Click a name (or your own name, I was logged in with a second browser) to start a call.
 4. Allow camera and microphone.

Expected result:
  Call connects and self view is visible.

Actual result:
  Could not acquire local media. Please check your settings.

Call-handleLocusResponse: Error on sendMeeting request DOMException: "The object could not be cloned."
Call-MakeCall: error while initiating cal DOMException: "The object could not be cloned."
MeetingClientActionCreators#Failed to get local stream TypeError: "this.error is null"
setCallJoinFailureMetrics
TypeError: n is null
mercury: error occurred in event handler TypeError: "n is null"
_updateRenderedComponent
Unhandled promise rejection TypeError: "n is null"
_updateRenderedComponent
mercury: error occurred in event handler TypeError: "n is null"
_updateRenderedComponent

Regression range:

17:48.27 INFO: Last good revision: 6646425c8cd10440f2ce38cd594be0c84a7c21fa
17:48.27 INFO: First bad revision: f6c89ca4944b0233e08463ce4825812c1b08373c
17:48.27 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=6646425c8cd10440f2ce38cd594be0c84a7c21fa&tochange=f6c89ca4944b0233e08463ce4825812c1b08373c

Wed Jun 06 00:48:50 2018 +0000	f6c89ca4944b	Andrew Swan — Bug 1369841 Make browser.runtime.onMessage and onConnect persistent r=zombie

Possibly a web compat timing issue? FYI

Comment 1

[Andrew Swan [:aswan]]

I don't have a webex account (nor am I interested in creating one), is there any simpler way to reproduce this?
The STR don't mention it, but does this require having a specific extension installed?

Comment 2

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

No extension is needed. Unfortunately, I know of no way to reproduce other than with an account, and since I couldn't figure out how to change my password, I'm reluctant to share my account. Maybe Arun can help, or help reproduce?

Comment 3

[Nils Ohlmeier [:drno]]

@aswan: if I'm not mistaken you should simply be able to create yourself an account with your @mozilla.com email address on https://teams.webex.com

FYI I'm also hitting this bug all the time.

Comment 4

[Liz Henry (:lizzard) (relman/hg->git project)]

Happy to take a patch in nightly 67, or potentially, in beta 66 for this.
Marking as fix-optional to remove it from weekly regression triage, since there is a priority assigned.

Comment 5

[Neha Kochar [:neha]]

Bulk change for all regression bugs with status-firefox67 as 'fix-optional' to be marked 'affected' for status-firefox68.

Comment 6

[Liz Henry (:lizzard) (relman/hg->git project)]

Just noticed this - we already removed this from triage.
Removing again (we shouldn't make these bulk changes without checking the previous status)

Comment 7

[Byron Campen [:bwc]]

This seems pretty reproducible still, we probably don't need any help reproducing.

Comment 8

[Raluca Popovici, Desktop QA]

This bug is still reproducible on MacOS 10.15 on Nightly 76.

Comment 9

[Byron Campen [:bwc]]

I cannot get teams.webex.com to work on any browser, because it will not let me call (or meet with) myself, nor will it allow me to dial a phone number. We need to get someone from webex involved here.

Comment 10

[Kohei Yoshino [:kohei]]

I just tested this. When you try to call yourself, the app shows the “couldn’t acquire local media” error message, but calling someone else seems working. You can simply use your Gmail’s plus sign aliases for testing. The app should instead say “you cannot call yourself” for a better UX.

Comment 11

[Emil Ghitta, QA [:emilghitta]]

Hi Kohei,

The "couldn't acquire local media" error message seems to also be displayed when you try to call someone else. With a note that you may have to firstly interact with the "Start Video" or "Start with Audio" buttons before dismissing the camera & mic permission panel in order to reproduce this issue.

For me, sometimes, when I reproduce this behavior the call never gets initiated and the error message keeps on spamming the window.

I've created a screencast but I think that it exceeds the size limit for bugzilla. You can view it here