NEW 246331
[iPhone 14] User cannot unmute WebRTC call and loses incoming and outgoing audio after receiving PSTN call and declining it
https://bugs.webkit.org/show_bug.cgi?id=246331
Summary [iPhone 14] User cannot unmute WebRTC call and loses incoming and outgoing au...
Madara Freimane
Reported 2022-10-11 03:24:23 PDT
Summary: [iPhone 14] User cannot unmute WebRTC call and loses incoming and outgoing audio after receiving PSTN call and declining it Tested devices and browser: Bug is reproducible on: - iPhone 14 (16.02, build: 20A380) with Safari iPhone 14 (16.0.3, build: 20A392) with Safari Bug is not reprodudicible on: - iPhone 11 (16.02, build: 20A380) with Safari - iPhone 11 (16.03, build: 20A392) with Safari Use case: Preconditions: Users (also iPhone 14 User) are in active audio/video WebRTC call Steps: 1. iPhone 14 User receives a PSTN call 2. iPhone 14 User declines the PSTN call 3. iPhone 14 User tries to unmute the WebRTC call Actual result: Incoming and outgoing audio disappears and iPhone 14 User cannot unmute WebRTC call (unmute button not responding) Expected result: WebRTC call goes to "unmuted" state automatically after the PSTN call. Remote participants in the WebRTC call can hear iPhone 14 User again. Reproducibility: 100% Additional information: -Sysdiagnostics file added: https://drive.google.com/file/d/181R5Tou-8x4Qryb8tQW4l2-W-kniRrTW/view?usp=sharing
Attachments
Radar WebKit Bug Importer
Comment 1 2022-10-18 03:25:17 PDT
Madara Freimane
Comment 2 2022-10-26 04:04:13 PDT
Bug is still reproducible Tested device: iPhone 14 | iOS 16.1, build: 20B82
Madara Freimane
Comment 3 2022-11-11 08:11:00 PST
Bug is still reproducible on iPhone 14 (iOS 16.1.1, build 20B101) with Safari
Madara Freimane
Comment 4 2022-11-15 10:20:51 PST
Hi, @Youenn! I am not able reproduce this bug anymore with iOS 16.2 Beta 2, build: 20C5043e, iPhone 14.
Madara Freimane
Comment 5 2022-12-15 08:13:43 PST
Fixed => Bug is not reproducible anymore. Tested device: - iPhone 14, iOS 16.2, build: 20C65 Thanks!
Joyce Ma
Comment 6 2023-01-19 14:14:57 PST
This issue is still reproducible after the second PSTN call rejection on 16.2. However, it is fixed for the initial call. Are there any updates for this bug?
Note You need to log in before you can comment on or make changes to this bug.