Closed waplay closed 2 years ago
Hi @waplay , this may be a bug in wortise. I tried to track it down, but wortise is unfortunately not open source so I can't take a look without reverse engineering the code. The wortise flutter plugin also doesn't have a GitHub page to report issues. I guess if you are a customer, you can talk to them directly.
Although I can't see how wortise is working under the hood, I can just say that the receiver should be unregistered when the activity is gone. audio_service may still keep the FlutterEngine around beyond this point, though, so if wortise is waiting for the engine to be destroyed before unregistering the receiver, then it is doing the wrong thing.
Thanks @ryanheise . I will try to talk to support Wortise.
Wortise solved the problem on his side. Can be closed.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs, or use StackOverflow if you need help with just_audio.
Which API doesn't behave as documented, and how does it misbehave? just_audio_background 0.0.1-beta.7
I have the problem that I get a native Android exception when I completely close the App. This problem only occurs if the app uses just_audio_background and ads SDK. In other applications without just_audio_background there is no error.
Minimal reproduction project Modified example
To Reproduce (i.e. user steps, not code) Steps to reproduce the behavior:
Error messages
Expected behavior Closing the app without error.
Screenshots No screenshots needed
Desktop (please complete the following information):
Smartphone (please complete the following information):
Flutter SDK version
Additional context -/-