Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Web mobile compatibility #445

Open
wants to merge 12 commits into
base: master
Choose a base branch
from
Open

Web mobile compatibility #445

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
4496ef7
update web sdk mobile compatibility
lynnfirst Jan 19, 2022
d6bd573
update web mobile compatibility
lynnfirst Jan 19, 2022
e9a4528
update web sdk mobile compatibi
lynnfirst Jan 20, 2022
89d8c56
update web mobile compatibility
lynnfirst Jan 20, 2022
a62b567
fix
lynnfirst Jan 20, 2022
ea61b9c
minor edit
lynnfirst Jan 21, 2022
9dcc5fc
add note
lynnfirst Jan 21, 2022
422c241
Merge branch 'heads/master' into web-mobile-compatibility
lynnfirst Jan 26, 2022
3f7ab14
rename and update according to review comments
lynnfirst Jan 26, 2022
c33e00d
add moble known issues en
lynnfirst Jan 27, 2022
eda24d5
change title
lynnfirst Jan 27, 2022
c7638d7
editorial review updates
lynnfirst Feb 9, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
333 changes: 333 additions & 0 deletions en-US/markdown/Video/web_sdk_mobile_known_issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,333 @@
# Known Issues and Workarounds on Mobile Devices

This page lists the known issues and limitations of using the Web SDK on mobile devices:
- Known issues: Caused by bugs on specific versions of iOS or specific browsers on Android. For some known issues, Agora provides workarounds.
- Known limitations: Unsupported APIs or features due to issues on iOS or Android.

<div class="alert info">Note that this page is continuously updated as Android and iOS evolve.</div>

## Known issues

### iOS

<details>
<summary>iOS 15.1.x: The browser crashes when sending the H.264 video stream</summary>
<p>

**Impact**: All browsers and apps that use WkWebView on iOS 15.1.x, such as Safari and Chrome.
</p>
<p>

**Details**: If you set `codec` as `'h264'` when calling `createClient`, the browsers on iOS 15.1.x crash after you send the video stream.
</p>
<p>

**Reason**: This issue happens due to the regression of the WebKit video encoder on iOS 15.1.x. For details, see [WebKit Bug 231505](https://bugs.webkit.org/show_bug.cgi?id=231505).
</p>
<p>

**Workaround**: Use the VP8 codec for video encoding.

```javascript
createClient({codec:'vp8', mode})
```
</p>
</details>

<details>
<summary>iOS 15.x: Low audio volume</summary>
<p>

**Impact**: All browsers and apps that use WkWebView on iOS 15.x, such as Safari and Chrome.</p>
<p>

**Details**: On iOS 15.x, after the local user subscribes to the `RemoteAudioTrack` and plays it, sometimes the audio is routed to the earpiece instead of the speaker, and the volume that the local user hear may be very low.</p>
<p>

**Reason**: This issue happens due to the regression of the WebKit audio module on iOS 15.x. For details, see [ WebKit Bug 230902](https://bugs.webkit.org/show_bug.cgi?id=230902).
</p>
<p>

**Workaround**: On iOS 15.x, use `WebAudio` to play the audio, and use `GainNode` to increase the audio volume level. Use the following workaround:
1. Upgrade to the Web SDK 4.9.0 or later versions.
2. Set the SDK private parameter `REMOTE_AUDIO_TRACK_USES_WEB_AUDIO` as `true`. The SDK uses `WebAudio` to play the remote audio stream. Sample code:
```javascript
function isIOS15(ua){
// Use UA to judge whether the iOS version is 15
}

if(isIOS15(navigator.userAgent)){
AgoraRTC.setParameter("REMOTE_AUDIO_TRACK_USES_WEB_AUDIO", true);
}
```
</p>
</details>

<details>
<summary>iOS 15.x: The video playback goes black</summary>
<p>

**Impact**: All browsers and apps that use WkWebView on iOS 15.x, such as Safari and Chrome.
</p>
<p>

**Details**: On iOS 15.x, if you play the video in DOM node and add some CSS properties (such as `transform` and `animation`) to the` video` element or its parent element, or if you change the CSS properties to redraw the video rendering area, sometimes the video goes black.
</p>
<p>

**Reason**: This issue happens due to the regression of the WebKit video renderer on iOS 15.x. For details, see [WebKit Bug 230902](https://bugs.webkit.org/show_bug.cgi?id=230902).
</p>
<p>

**Workaround**: Upgrade to the Web SDK v4.7.3 or later and minimize changes to the CSS properties of the `video` element and its parent elements.
</p>
</details>


<details>
<summary>iOS 15.x: If a user wears a Bluetooth headset, the audio may be significantly distorted</summary>
<p>

**Impact**: All browsers and apps that use WkWebView on iOS 15.x, such as Safari and Chrome.
</p>
<p>

**Reason**: This issue happens due to the regression of the WebKit audio playback module on iOS 15.x. For details, see [WebKit Bug 231422](https://bugs.webkit.org/show_bug.cgi?id=231422).
</p>
<p>

**Workaround**: Agora recommends that you add a prompt to remind users of possible audio distortion issues when they use a Bluetooth headset.
</p>
</details>

<details>
<summary>iOS 15.x: Backgrounding the browser or app causes the audio streaming to be cut off.</summary>
<p>

**Impact**: All browsers and apps that use WkWebView on iOS 15.x, such as Safari and Chrome.
</p>
<p>

**Reason**: This happens primarily due to this WebKit [bug](https://bugs.webkit.org/show_bug.cgi?id=231105). After the browser switches to the background, the `AudioContext` of `WebAudio` stops processing audio.
</p>
<p>

**Workaround**: Follow these steps to avoid this issue:
1. Upgrade to the Web SDK v4.7.3 or later versions.
2. When calling `createMicrophoneAudioTrack`, set `bypassWebAudio` as `true`. The Web SDK directly publishes the local audio stream without processing it through `WebAudio`.

```javascript
const localAudioTrack = await AgoraRTC.createMicrophoneAudioTrack({bypassWebAudio: true});
```

> Note that this workaround has a side effect. After applying this workaround, the audio mixing function (`MixingAudioTrack`) in the SDK fails.
> </p>
> </details>

<details>
<summary>iOS 15.x: Audio and video playback might not resume automatically after being interrupted by a system phone call, another real-time interaction app, Siri, or an alarm.</summary>
<p>

**Impact**: All browsers and apps that use WkWebView on iOS 15.x, such as Safari and Chrome.
</p>
<p>

**Reason**: Such interruptions can cause the state of the `video` and `audio` elements to be `paused`. After the interruption finishes, the state cannot be automatically switched back to `playing`, and even calling `HTMLMediaElement.play` cannot resume the media playback. See the WebKit bug [232599](https://bugs.webkit.org/show_bug.cgi?id=232599) and [226698](https://bugs.webkit.org/show_bug.cgi?id=226698) for more details.
</p>
<p>

**Workaround**: Upgrade to the Web SDK v4.7.3 or later versions. The SDK attempts to resume media playback after the interruption. Agora recommends that you add a prompt that instructs users to refresh the page.
</p>
</details>

<details>
<summary>Other known issues</summary>
<p>

- The volume of a remote user can change randomly on iOS 13 and 14.
- Switching between the front and rear cameras can momentarily rotate the video.
- The audio routing can change randomly. Sometimes, the audio is routed to the speakerphone when a headset is connected or to the earpiece when no headset is connected.
- If you call `getUserMedia` twice to get two tracks of the same media type, the first track goes muted or black.
- After a user switches to another app that uses the microphone or camera (such as Siri or Skype) and then switches back, the audio sampling or video capture fails.
</p>
</details>

### Android

<details>
<summary>Android 12: Video distortion on Chrome when hardware acceleration is enabled</summary>

<p>

**Impact**: The Chrome browser or Chromium kernel browser 97 or earlier on certain devices with Android 12, such as Pixel 3 and Pixel 4.
</p>
<p>

**Details**: If the Chrome browser on Android 12 enables the WebRTC `H264` or `VP8` hardware acceleration by default, video distortion can occur.
</p>
<p>

**Reason**: This issue happens due to the regression of the Chromium WebRTC video encoder. For details, see [Chromium issue 1237677](https://bugs.chromium.org/p/chromium/issues/detail?id=1237677).
</p>
<p>

**Workaround**: Chrome 97 fixed this issue. You can instruct users to upgrade to Chrome 97 or later versions.
</p>
</details>

<details>
<summary>The bitrate when sending video on Android Chrome fails to reach the preset value.</summary>
<p>

**Scope**: Certain Android devices, such as Xiaomi and OnePlus.
</p>
<p>

**Reason**: This is a hardware encoder issue. The bitrate fails to reach the preset value at a specific video encoding frame rate.
</p>
<p>

**Workaround**: In most cases, the bitrate is relatively lower when the frame rate is set as 15 fps. If you set the frame rate as 30 fps, the bitrate increases. So Agora recommends trying to set the frame rate as 30 fps when encountering a bitrate issue. However, setting the frame rate as fps may cause performance issues.
</p>
</details>

<details>
<summary>The autoplay of inaudible media is blocked on WeChat</summary>
<p>

**Impact**: The WeChat browser using Chromium 89 kernel
</p>
<p>

**Details**: The autoplay of inaudible media is blocked. Even after the user interacts with the webpage to resume the video playback, the autoplay block is still not removed.
</p>
<p>

**Reason**: This issue happens because the WeChat browser implements a custom autoplay policy.
</p>
<p>

**Workaround**: Follow these steps to avoid this issue:
1. Upgrade to the Web SDK v4.6.0 or later versions.
2. Listen to the `AgoraRTC.onAutoplayFailed` event. Instruct the user to click on the page to resume playback:

```javascript
AgoraRTC.onAutoplayFailed = ()=>{
document.alert('Please click the page to resume playback');
}
```
</p>
</details>

<details>
<summary>If a local user wears a Bluetooth headset, after they start to send the audio, the remote audio is lost</summary>
<p>

**Scope**: Certain Xiaomi and OnePlus devices
</p>
<p>

**Details**: If a local user wears a Bluetooth headset, when the Bluetooth headset starts capturing the audio, there is a possibility that the remote audio is lost.
</p>
<p>

**Reason**: It may be due to the audio issue on Chromium regarding the profile switch of the Bluetooth.
</p>
<p>

**Workaround**: Agora recommends that you add a prompt to remind users of possible audio-loss issues when they use a Bluetooth headset.
</p>
</details>

<details>
<summary>Issues specific to certain Android devices</summary>
<p>

- On devices equipped with **MediaTek chips**, the Web SDK cannot encode and send video streams in H.264.
- On devices equipped with Huawei **HiSilicon Kirin** chips, if you use Chrome versions earlier than 88, the Web SDK cannot encode and send video streams in H.264.
- When receiving video streams on Chrome on **OnePlus 6**, if the screen turns off, the video can freeze.
- **Harmony OS** does not support sending the video stream of 180p.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe "at 1080p"? (fix CN also, if so)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, this is 180p

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay!

</p>
</details>

<details>
<summary>Other known issues</summary>
<p>

- On some Android devices, the device labels might not be available.
- On some Android devices, tracks can end if the audio and video streams are interrupted by system phone calls or other audio or video calling apps. To resume the call, the Web SDK needs to re-capture the audio and video.
- On Android Chrome, the Web SDK cannot send high-quality and low-quality streams in H.264.
- On Android Chrome earlier than 90, the volume obtained by `getVolumeLevel` is 0, but the user can hear the audio.
- On Android system Webview versions from 55 to 75, the `decodeFrameRate` property stays 0.
</p>
</details>

## Known limitations

### iOS

<details>
<summary>The <code>createScreenVideoTrack</code> method is not supported</summary>
<p>

Reason: iOS Safari and WkWebView do not support the `mediaDevices.getDisplayMedia` method.
</p>
</details>

<details>
<summary>The <code>setBeautyEffect</code> method is not supported</summary>
<p>

Reason: WebGL is not well supported on iOS Safari and WkWebView, and the image enhancement algorithm can reduce the system performance below acceptable levels.
</p>
</details>

<details>
<summary><code>The IBufferSourceAudioTrack.seekAudioBuffer</code> method is not supported</summary>
<p>

Reason: `WebAudio` on iOS does not support this method.
</p>
</details>

<details>
<summary>Cannot send H.264 video streams with a resolution of 1080p or higher</summary>
<p>

Reason: The Web SDK uses the H.264 Baseline Profile for negotiation, so encoding and sending a video stream with a resolution of 1080p or higher is not supported on iOS.
</p>
</details>

<details>
<summary>When sending a low-quality stream on iOS Safari, you cannot set <code>LowStreamParameter.bitrate</code>, and the resolution of the low-quality stream must be proportional to the resolution of the high-quality stream.</summary>
<p>

Reason: iOS Safari and WkWebView do not support setting the frame rate with the `RTCRTPSender.setParameters` method. After compressing the resolution with the `scaleResolutionDownBy` property, the resolution of the low-quality stream stays proportional to the resolution of the high-quality stream.
</p>
</details>

<details>
<summary>The <code>encodeDelay</code> property is not supported</summary>
<p>

Reason: The `encodeDelay` property cannot be calculated through the `getStats` method of WebRTC on iOS.
</p>
</details>

### Android

<details>
<summary>The <code>createScreenVideoTrack</code> method is not supported</summary>
<p>

Reason: The `mediaDevices.getDisplayMedia` method is not implemented on mobile browsers and WkWebView.
</p>
</details>

<details>
<summary>The <code>setBeautyEffect</code> method is not supported</summary>
<p>

Reason: The image enhancement algorithm can reduce the system performance of mobile devices below acceptable levels.
</p>
</details>
Loading