This bug report is about the live page on TWiT with Chrome on macOS.
I select the “TuneIn…” player from the dropdown menu:
The player buffers for a few seconds.
Then, it shows an error “there was a problem loading the player”.
In the the developer console, I see the following error:
Uncaught (in promise) DOMException: play() failed because the user didn't interact with the document first.
It could be a new Chrome anti-autoplay feature interfering with the TuneIn script. Maybe updating the TuneIn embed code might help?
As I never used it in the past, I don’t know how it’s supposed to work but if you let it time out the first time and then click “Retry” it immediately connects. So I guess the error diagnostic is correct, it just wants to know you’re willing to interact with it. As I was experimenting, I even got an preroll ad though.
@Leo and/or @PDelahanty will have to check if there is something that needs fixing (assuming it can be.)
Yes, it works for me when I try to reconnect as well. So reconnecting every time would be enough to have a somewhat usable player. The same is true for the TuneIn “popout” player.
The TuneIn player works fine in Safari. I believe the player has been built with this kind of autoplay being allowed, and just never updated since Chrome made the change.
Update: This error seems to have fixed itself. It still doesn’t autoplay even though autoplay is enabled in the TuneIn embed, but at least now it doesn’t show an error anymore.
