Midori Kochiya

Can confirm that the service is started normally with correct notification after this change.

I opted not to close this issue as the original problem seems to be still there.

I have tried to implement a custom `StreamAudioSource`, the progress has been good so far. However, I noticed that the proxy always returns `200` or `206` without any way to...

I personally think that it is enough to have a way to indicate that "something went wrong when generating the response" by grabbing the error from the returned future in...

Uh...now that you say it, probably not (we probably should not cache HLS in this way?). It should be fine to return a 500, just like how these extemely simple...

If memory serves me right, there’s indeed problems in MIME handling when I was adapting the code to my business logic (it wasn’t being written properly), I’m looking into opening...

Now that `audio_service` has been moving to an approach that runs all code in the same isolate, I'm worried that all the `existsSync` operations in `LockCachingAudioSource` might cause unwanted problems...

@zhangruiyu M4A works differently from MP3 as the player needs to access data at the end of the file (because of how the container works by default), which hits a...

@zhangruiyu I can personally tell you how to troubleshoot this, but please leave other discussions there so the author and others can fix the issue (I think we DO have...

I've noticed random network failures (connection errors) when playing in background on iOS, but have no idea if this is something on my device (we are only beta testing on...