When HTML5 audio finishes playing, the .ended event doesn't fire if the web app is running in the background or if the screen is off. Here's a simple page that demonstrates the problem: http://bitshuvafiles01.com/iOSAudioBugRepro/audioError.html Steps to reproduce: 1. Create web page with a single <audio> element. 2. In JavaScript, set audio.src = "song1.mp3", and .play(); 3. Add an .ended event handler to the audio element. In the .ended event handler, set audio.src = "song2.mp3", and .play(). 4. While song1.mp3 is playing, turn off the phone screen. 5. Wait for the audio to finish. When it finishes, audio will stop; song2.mp3 will never. Expected results: The audio.ended event fires and the next song starts playing. Actual results: The audio.ended event never fires because the screen is off or because Safari is in the background; JS execution is suspended. Additional info: While suspending JS execution is wise for battery life reasons, it harms the user experience when listening to audio on the web. Either don't suspend JS execution for tabs playing audio, or at least fire the .ended event so we can play the next song.
<rdar://problem/32757402>
The web proces, normally suspended when in the background, is kept alive while playing audio (and for a few other reasons). The 'ended' event is fired asynchronously, so while the event is scheduled immediately when playback finishes, the task is suspended before the next runloop so the event doesn't fire until the process resumes. We should probably postpone suspension for a few cycles when playback stops to give scripts an opportunity to restart playback.
>> "We should probably postpone suspension for a few cycles when playback stops to give scripts an opportunity to restart playback." Ah, that would wonderful and would fix the problem perfectly.
Hi any idea when this could be committed and it starts to hit upstream?
(In reply to craigwharding from comment #4) > Hi any idea when this could be committed and it starts to hit upstream? There's nothing to be committed because there's no patch yet. (This is an open source project)
This morning I received more reports of this same bug from my users on iOS. Any chance we get this fixed in 2018?
Confirmed still an issue.
*** Bug 204080 has been marked as a duplicate of this bug. ***
Created attachment 383493 [details] Patch
Comment on attachment 383493 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=383493&action=review r=me once the bots are happy > LayoutTests/media/audio-background-playback-playlist-expected.txt:2 > +RUN(internals.setMediaElementRestrictions(audio, "RequireUserGestureForAudioRateChange")) Oops, look like you need to regenerate this file. > LayoutTests/media/audio-background-playback-playlist.html:20 > + run('audio.load()'); > + testExpected('internals.bestMediaElementForShowingPlaybackControlsManager("NowPlaying")', audio); It would be better to test for NowPlaying status after a delay, e.g. after an 'emptied' event.
Created attachment 383656 [details] Patch for landing
Comment on attachment 383656 [details] Patch for landing Clearing flags on attachment: 383656 Committed r252692: <https://trac.webkit.org/changeset/252692>
All reviewed patches have been landed. Closing bug.
I’m getting this bug in iOS 15.3.1. It was fixed for me in iOS 14. Should I add info to this bug or open a new one and reference this bug?
Hi, I am getting this bug again too in Safari in iOS 15. After screenlock, the JS execution is still continuing after the ended event on the audio element as console.log pumps out text. I set new src and call .play(). The promise for .play() resolves without errors, but audio does not play. The Media Sessions API also sets the correct track name/title. An example is here (not mine as mine is behind a paywall but I can create a minimum reproducible example if required): https://codepen.io/craigstroman/pen/aOyRYx To reproduce using the above example link: 1) Play the first track 2) Lock the screen 3) Wait around 3 minutes for the track to end Expected result: The next track should play automatically after ended event. Actual result: The next track does not play in iOS 15 Safari. Works fine in Android/Windows Chrome. What I have tried: changing the src and calling the play event directly inside the audio element's ended event. But all this only works when Safari is in focus, bot when in another app, or screen is locked. Would appreciate any help on this - I am at my wits end. Thanks!
I'm still experiencing this in iOS 15.4.1. Both in browser and when running a site as a "home screen bookmark". Initially I got it working by having a function (initTrack()) that ran each time the user pressed played manually. The "ended" event listener was added within that function and all it did was to run initTrack() again. But all of a sudden it stopped working. The audio widget seems to reset it's currentTime and the Media Session API is changing the metadata, but before the new track starts playing, it seems like the sessions gets suspended.
I just want to add my experience with this too (on 15.4.1). My experience is slightly different than the bug title, because when the track ends, mine does appear to briefly switch to the next track and update the new mediaSession MediaMetaData, though fails to actually start playing that track and the new track goes away in less than a second. So I suspect that the _ended_ event _does_ fire, but it maybe doesn't seem to have permission to play() the next track? Also, when testing, I once found that my track stopped playing after a half-hour. I haven't done more testing to see if that always happens or not.
The inability to begin playing in the background on iOS 15 should be fixed by the changes for 239812.
(In reply to Eric Carlson from comment #18) > The inability to begin playing in the background on iOS 15 should be fixed > by the changes for 239812. Rather by r293530, bug https://bugs.webkit.org/show_bug.cgi?id=239812
Thanks Eric! Do you know what iOS 15 release this will merged into?
(In reply to craigwharding from comment #20) > Thanks Eric! Do you know what iOS 15 release this will merged into? Sorry, I don't know. I will try to remember to add a note here when a build with this fix is available.