You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/known-issues.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,18 @@ This article provides information about limitations and known issues related to
22
22
23
23
The following sections provide information about known issues associated with the Communication Services JavaScript voice and video calling SDKs.
24
24
25
+
### iOS 16 introduced bugs when putting browser in the background during a call
26
+
The iOS 16 release has introduced a bug that can stop the ACS audio\video call when using Safari mobile browser. Apple is aware of this issue and are looking for a fix on their side. The impact could be that an ACS call might stop working during a call and the only resolution to get it working again is to have the end customer restart their phone.
27
+
28
+
To reproduce this bug:
29
+
- Have a user using an iPhone running iOS 16
30
+
- Join ACS call (with audio only or with audio and video) using Safari iOS mobile browser
31
+
- If during a call someone puts the Safari browser in the background and views YouTube OR receives a FaceTime\phone call while connected via a Bluetooth device
32
+
33
+
Results:
34
+
- After a few minutes of this situation, the incoming and outgoing video may stop working.
35
+
- The only way to get ACS calling to work again is to have the end user restart their phone.
36
+
25
37
### Chrome M98 - regression
26
38
27
39
Chrome version 98 introduced a regression with anormal generation of video keyframes that impacts resolution of a sent video stream negatively for majority (70%+) of users.
0 commit comments