ryanheise
ryanheise
Unfortunately not, if I knew how to detect this, it would be an easy next step to make an official fix. In the code, you'll see that there's a boolean...
You can try calling `stop` or `dispose` to remove the notification. The actual code responsible for creating/destroying the notification is in the audio_service package.
The place to check if you were to dig into the code is `audio_service/darwin/Classes/AudioServicePlugin.m` if you search for the method name "stopService". Inserting a log in there may reveal whether...
Thanks for reminding me. Can you test the `fix/unimplemented_methods` branch and see if it fixes your issue?
Can you check whether `stop` is at least being called now?
I'm not quite sure if I understand your answer. You're answering "No, but sometimes yes". Is that correct? Can you describe the circumstance more clearly where stop is called?
Stop is called on insert? That's strange, I am not aware of any code path from insert to stop. Unless an error has occurred during load, perhaps...
Can you copy and paste the error?
That could be helpful, particularly if you can provide a minimal reproduction project.
Regarding the behaviour of inserting through the entire playlist, you can test the treadmill branch which implements an experimental version of lazy loading for iOS.