[Webkit-unassigned] [Bug 246340] [iPhone 14] Outgoing video does not recover for WebRTC call if the User goes to another app, plays a video and navigates back to browser

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Nov 16 09:44:00 PST 2022


https://bugs.webkit.org/show_bug.cgi?id=246340

Madara Freimane <madara.freimane at testdevlab.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[iPhone 14] Incoming and    |[iPhone 14] Outgoing video
                   |outgoing audio disappears   |does not recover for WebRTC
                   |for WebRTC call if the User |call if the User goes to
                   |goes to another app, plays  |another app, plays a video
                   |a video and navigates back  |and navigates back to
                   |to browser                  |browser

--- Comment #4 from Madara Freimane <madara.freimane at testdevlab.com> ---
Hi!

Using the same use case, behaviour is different with last available iOS 16.2 Beta 3 version, now incoming and outgoing audio recovers, but only outgoing video does not recover when User navigates back to WebRTC call, for example, from Youtube app.

Because of that I changed title of the ticket and added a new sysdiagnostics file:
https://drive.google.com/file/d/16kOqvB50kEqwYaClnXCIfsKDIofuqrW9/view?usp=share_link

Same use case:
Preconditions:
Users are in active WebRTC video call

Steps:
1. User goes to YouTube and plays video OR goes to another app, for example, Facebook and plays a video
2. User navigates back to WebRTC call (opens Safari)
=> Outgoing video does not recover for WebRTC call if the User goes to another app, plays a video and navigates back to browser. Camera is turned OFF and other User still can see frozen video/black video.

Tested devices:
Bug is reproducible on:
iPhone 14 | iOS 16.2 Beta 3, build: 20C5049e

Bug is not reproducible on:
iPhone 11 Pro Max | iOS 16.2 Beta 3, build: 20C5049e

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20221116/49deef8b/attachment-0001.htm>


More information about the webkit-unassigned mailing list