Simple repro site at https://ios-standalone-bug.backgroundnoise.app
1. Write a web app that Includes an HTML <audio> element
2. Pin it to home screen on iOS with display:standalone in manifest.json
3. Launch the web app
4. Play the audio
5. Leave the web app
Audio keeps playing
Audio stops playing.
NOTE: If you play the audio in Safari and leave Safari it keeps playing in the background. This only affects standalone web apps/PWAs
I'm also having this problem on https://podcatcher.app/
Please get this on somebody's list. We have a very popular PWA with limited functionality on iOS 13 due to no background audio!
We use WKWebView in our app, and we also have this bug. I've looked sources for a little, and it seems that it is not actually a webkit bug, but something in iOS. Safari manages media via some complicated mechanisms, so it doesn't reproduces there.
Please get somebody to work on the fix for this issue, this bug blatantly prevents users to have the same experience as native app users.
Same Problem on my progressive Web app based on audio content. It was perfectly working with previous IOS. It's a huge step backwards for user experience.
This is a big problem for our PWA, as well.
I'm having this issue also we need to develop an only native app for Apple other support audio in the backgroung
I'm also having this problem on https://podcasts.ba-ba-bam.com/be-lively-lexperience-bien-etre/
Hi everyone, just a quick update: we have been investigating this issue but don’t yet have a solution. We understand that the current behavior blocks a lot of important use cases. But because the issues causing this behavior may be due to the underlying platform, investigation is being tracked inside Radar, rather than here on bugzilla. If we do identify a fix, we’ll ping this thread when that fix is available for testing. Thanks for your patience.
(In reply to Jer Noble from comment #10)
It is wonderful to hear that this issue is being investigated! Thank you for your hard work. Is there a link to the bug report on Radar, so that I can track the progress?
Following some internal info trails, I believe this is a dupe of https://bugs.webkit.org/show_bug.cgi?id=205687 and thus resolved (but not yet in a release). I will confirm with an internal build before duping, and I’ll see what we can do about getting the fix in an update.