Bug 274385

Summary: [WebXR] AudioContext not playing audio after XR session is started
Product: WebKit Reporter: connell
Component: WebXRAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: adachan, cdumez, djg, jer.noble, mwyrzykowski, sorenlef, tr, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: Safari 17   
Hardware: Vision Pro   
OS: visionOS 1   
Attachments:
Description Flags
Test case showing AudioContext issue on AVP none

Description connell 2024-05-20 04:04:41 PDT
We've found tha AudioContexts don't appear to output audio after an XR session is started. Calling 'resume()' on the context after the session as started unfortunately does not help.
Comment 1 Alexey Proskuryakov 2024-05-22 10:49:17 PDT
Than k you for the report. Would it be possible to provide a reproducible test case, so that we don't have to re-create it from the description?
Comment 2 Radar WebKit Bug Importer 2024-05-27 04:05:13 PDT
<rdar://problem/128788609>
Comment 3 connell 2024-05-29 02:43:53 PDT
My apologies for the delay. I'll have access to our AVP tomorrow and will provide a test case.
Comment 4 connell 2024-05-31 05:50:59 PDT
Created attachment 471552 [details]
Test case showing AudioContext issue on AVP

This index.html file has two buttons. Clicking the first starts an AudioContext and plays a sine wave. (Sorry for how annoying the sound its but it's easier than attaching an audio file). The second button starts an XR session. Note that, for simplicity, the file does not set up any 3D rendering, it just requests the session.
On AVP clicking the first button starts the audio playing, but when the second button is clicked (and the XR sessions starts) the audio stops playing.
On the Quest and PICO browsers the audio continues to play once the session is started.
Comment 5 connell 2024-06-11 05:43:06 PDT
Just a wee note to say that this appears to be fixed in the Vision OS 2 preview build :-)
Comment 6 Ada Chan 2024-06-11 09:56:22 PDT
Probably fixed by https://bugs.webkit.org/show_bug.cgi?id=269332

*** This bug has been marked as a duplicate of bug 269332 ***