Affected versions

• 95.0a1 (2021-10-19)
• 94.0b8(20211019190240)

Affected platforms

• macOS 12 (beta 21A5552a)
• macOS 11.6

Steps to reproduce

1. Launch the browser.
2. Go to https://jump.chat/ and create a room.
3. Connect your headset to the device.
4. Grant audio and video permissions.
5. Unplug the headset during the call.
6. (notice loss of audio input)
7. Plug the headset back.
8. (notice loss of audio input)

Expected result

• Switching between the audio input from the headset to the internal microphone should be done without any issues.

Actual result

• Unplugging the headset during call will render the audio input to be lost for the remainder of the call (be it internal or headset input)

Suggested Severity

• Seeing as how this issue only occurs on a specific device architecture, as well only managing to reproduce it on one webRTC website, I would rate this an S3.

Regression range

• Will return with regression ASAP.

Additional notes

• Managed to reproduce this issue only on a macOS platform with ARM architecture (macBook Air M1, 2020)

This is not a regression, I can reproduce it all the way to Firefox 73 (on older versions than Firefox 73, the chat room is not loading).
Reproduced it also on Chrome Version 95.0.4638.54 and Safari 15.0.

This issue is still reproducible on Macos 11 and MacOS 10.15 but after plugging the headsets, the mic is not switched, it remains the internal microphone.

Hello,

This issue is still reproducible on MacOS 11 using Nightly 101.0a1 (2022-04-05) on https://whereby.com. The loss of audio input is observable upon unplugging and even after plugging back the headphones.

This issue is also reproducible on Ubuntu 22.04 with firefox 102.0 with usb headset.