ryanheise

I should mention that the reproduction project at the top of this thread is slightly artificial because the prefetch button directly interacts with the audio source's request method rather than...

I am surprised if an unhandled exception would be the actual cause. Last time I looked at the flutter codebase, these exceptions are caught, and the stacktrace is printed out...

@ndmgrphc You are right that this is a more general issue for anyone using the proxy. Please make sure you are testing the branch mentioned above with the developments intended...

@ndmgrphc please confirm whether you have tested the `fix/caching` branch which already attempts to catch errors and restart the proxy.

@ndmgrphc if your app is crashing on line 799 then you may not be using this branch in the way it was intended, because there should not be any need...

@Colton127 The latest commit should handle the unhandled exceptions. I'm not convinced that this would fix any behavioural issues, only that it will suppress the unhandled exceptions messages in the...

> I also confirmed with breakpoints that the following cleanup code does not run - which is most likely why a new connection is not attempted (as hinted by the...

@agersant you can try replacing the last line of the request method by this: ```dart return byteRangeRequest.future.then((response) { response.stream.listen((event) {}, onError: (Object e, StackTrace st) { // So that we...

The latest commit on the `fix/caching` branch applies the above code snippet. Please try it and let me know if there are still issues. Note that with this code, there...

Thanks, @agersant for that comprehensive report. I am not sure whether the Test 3 behaviour is due to code within this plugin or code within the network stack, but there...