Bug 238388 – No audio (ringtone) if User receives incoming webRTC call while the browser is in the background

• Component: WebRTC
• Status: NEW

[Madara Freimane]

Created attachment 455780 [details]
sysdiagnose_2022.03.25_19-19-57+0200_iPhone-OS_iPhone_19E241.tar.gz

Summary:
No audio (ringtone) if User receives incoming webRTC call while the browser is in the background

Tested devices:
Bug is reproducible on:
*iPhone 12 Pro Max | iOS 15.2
*iPhone 11 | iOS 15.3.1
*iPhone 11 Pro Max | iOS 15.4


Scenario:
Precondition:
Safari is in the background

Steps:
1. User receives an incoming WebRTC call

Actual result:
No audio (ringtone) if User receives incoming webRTC call while the browser is in the background

Expected result:
There is an audio (ringtone) if User receives incoming webRTC call while the browser is in the background

Reproducibility:
100%

[Radar WebKit Bug Importer]

<rdar://problem/90919456>

[youenn fablet]

Hi Madara, can you tell how you play the ringtone?
There are some restrictions to play audio when a page is backgrounded.
Would you be able to provide a test case?

[Madara Freimane]

One of the use cases:
1. Create a call using https://web.skype.com/
2. Make outgoing call from another device to iOS device

Notes:
-If we compare behaviour with an Android: there is an ringtone and User knows that there is an incoming call on browser side.
-Also observed, that sometimes it's not possible to receive a call while browser is in a background.

[youenn fablet]

(In reply to Madara Freimane from comment #3)
> One of the use cases:
> 1. Create a call using https://web.skype.com/
> 2. Make outgoing call from another device to iOS device
> 
> Notes:
> -If we compare behaviour with an Android: there is an ringtone and User
> knows that there is an incoming call on browser side.
> -Also observed, that sometimes it's not possible to receive a call while
> browser is in a background.

Do you know which API is used to trigger the ringtone in iOS and Android?
When a tab is backgrounded, it might be suspended, meaning that JavaScript might not even be running. That might explain why the call cannot be made.
I guess the future solution might be a mix of push API and notification API.

[Renārs Ričards Hartmanis]

Hi!

It seems that the behaviour is acceptable because iOS Safari doesn't allow autoplay without user interaction, can't run in the background, and lacks access to native call features. So the ticket can be closed.

Thank you!