Closed arkjel closed 3 years ago
I resolved the issue! You can push the flag --use-fake-ui-for-media-stream directly to the chromium or firefox via args key:
const browser = await chromium.launch({ args: ['--use-fake-ui-for-media-stream'] });
You can put this information to the docs for future users :)
Thanks @arkjel - good to hear you've found the solution. We'll see about potentially adding more info in the docs.
Context:
Extra: Jest: 26.6.3
System:
Describe the bug
When I try to launch my test, I get the following error message. It occurs when I try to test my microphone in the waiting room to the meeting in my application (it is similar to the waiting room in the Google Meet when you can choose your microphone and camera). The app uses Twilio for video calls. The core issue you can see in that line:
Chromium:
[29603:83715:0311/101727.631315:ERROR:audio_rtp_receiver.cc(88)] AudioRtpReceiver::OnSetVolume: No audio channel exists.
Firefox:
console.warn: SearchSettings: "get: No settings file exists, new profile?" (new Error("", "(unknown module)")) [err] Exiting due to channel error.
Important notice:
Conclusion & Thoughts
Do you plan to implement these flags to the Playwright? They might fix my issue. What do you think?
Source: https://webrtc.github.io/webrtc-org/testing/
Error logs from Chromium:
➜ yarn test:e2e:local:start yarn run v1.22.5 $ dotenv -e .env.test -- yarn test:e2e:debug $ PWDEBUG=1 jest --config ./jest.config.json --detectOpenHandles FAIL e2e-tests/toDo/loginWithURL.spec.ts (65.696 s) Login to the Front ✕ Login as a Participant (62962 ms) ● Login to the Front › Login as a Participant page.click: Protocol error (Runtime.callFunctionOn): Browser closed. ==================== Browser output: ====================