ryanheise
ryanheise
Audio stream in Chrome does not return "ready" state after "stop" and "play". Bring only "buffering"
Can you update your issue with the correct link to the previous issue?
Audio stream in Chrome does not return "ready" state after "stop" and "play". Bring only "buffering"
Ah sorry the link was already correct! My mistake. As for the issue, I'm afraid I still don't have any further leads, though. I have also only tested Chrome. Have...
Audio stream in Chrome does not return "ready" state after "stop" and "play". Bring only "buffering"
That looks very helpful! Basically the first link suggests it's a timing issue. However, you can see in the code that this plugin does register the callbacks. The second link...
Audio stream in Chrome does not return "ready" state after "stop" and "play". Bring only "buffering"
It wasn't clear to me that @anfernandezz tested the workaround in the second stackoverflow link before you shared that link. But just to be clear, that is what is being...
Audio stream in Chrome does not return "ready" state after "stop" and "play". Bring only "buffering"
OK, then my previous response still applies, and the second link, while inelegant, seems like the only way to get it to work.
Audio stream in Chrome does not return "ready" state after "stop" and "play". Bring only "buffering"
To be clear, the solution requires modifying just_audio_web.
The currently used iOS API also provides access to non-ICY metadata, so it's a matter of collecting all of the additional metadata that you want into a data packet and...
I have changed this to a documentation request. There is a parameter to `init` called `androidNotificationIcon` where you can pass in the icon, but the icon is supposed to be...
Reopening since the documentation still hasn't been written.
The documentation currently just contains a reference to audio_service: https://pub.dev/documentation/just_audio_background/latest/just_audio_background/JustAudioBackground/init.html > Each parameter controls a behaviour in audio_service. Consult audio_service's AudioServiceConfig API documentation for more information. which I guess is...