ryanheise
ryanheise
I'm not at my computer right now but from memory the documentation for listen says that it takes these callbacks directly as parameters.
@AmmarZY we are figuring this out together, please feel welcome to join in and try out the numerous suggestions above as a starting point. You will need to make these...
@esiqveland 's code looks on the right track to me. (just fyi I'll be in hospital on Monday, so probably can't give it attention until after then.) Based on my...
@pro100svitlo Your problem may be different but once the issue is fixed for `LockCachingAudioSource` it should also automatically be fixed for your problem, too. All that's happening in both cases...
@pro100svitlo yes, but that too is something where the solution is going to be the same in both the caching and the headers cases.
On error, you would probably want to call `_playbackEventSubject.addError(...)`.
I've just been looking at this today, and strangely I have never experienced the proxy crashing and needing to be restarted. I do indeed get the exception stack trace listed...
If anyone wants to test the code in my previous comment, I have pushed it to a branch called `fix/caching`.
FYI, I intend to publish the above fix with or without testing within 24 hours, although of course I would appreciate if anyone can try the above fix before then.
Thanks for testing, @Colton127 . What exactly happens when you say it "causes the app to faulter"? How can I reproduce it?